3 Replies Latest reply on Nov 7, 2012 6:52 PM by cgrim

    Authorization Error in MVM API

      Hi, I am writing a script that will connect to an MVM API. I have a copy of the "MVM Open API" package (it's not very "open", but that's a conversation for a different day). I am still stuck on the authentication step. I have a SOAP request created as follows:


      I am developing this against a 60-day trial version of MVM; I am hoping that I can get this working so that I can give it to a client that has a full license for MVM.




      The error code -9 appears to be FSCOMM_BAD_SIGNATURE. Is the the correct error message, and if so, what signature is it referring to?


      The only signature that I am aware of is the signature on the SSL client certificate; I generated that certificate using the Foundstone Certificate Manager tool. I removed the passphrase from that certificate using OpenSSL FIPS Object Module v1.2 on the same server that I generated the certificate on.


      I enabled API logging in the registry and restarted the API service but it does not include any useful information in the log files.


      The error message also says "Not Authorized Access". I'm not sure what this means, either. I'm trying to authorize myself, I am only trying to authenticate.


      Finally, I'm confused by the "Customer" and "PortalName" fields. The "Customer" element is not explained AT ALL in the API documentation. The "PortalName" documentation only says, "A third-party SOAP client should store an empty string in this field." Therefore, I am putting an empty string in that field.


      Thanks for any insight that you can offer.