topic Re: CIM API requires clientID? in Integration and Testing

CIM API requires clientID?

kevinfairchild — Fri, 24 Feb 2017 17:10:26 GMT

After refreshing the definition for the SOAP web reference for https://api.authorize.net/soap/v1/Service.asmx?wsdl, I noticed that our previously-working code no longer compiles. In each instance, it looks the definition for the methods listed in the compile errors (CreateCustomerProfile, UpdateCustomerPaymentProfile, etc.) all have a string parameter of clientID that is expected (but wasn't in our earlier web reference definitions).

In looking at the CIM API docs (http://www.authorize.net/content/dam/authorize/documents/CIM_SOAP_guide.pdf) and the API reference (http://developer.authorize.net/api/reference/), neither mentions this field anywhere. Additionally, the sample code in the API reference matches our calls and doesn't seem to be passing in a clientID anywhere.

What is clientID and how should we be using it, now that it's required? Is that our userid, tran key, a unique id for that specific card, or what?

Re: CIM API requires clientID?

kevinfairchild — Fri, 24 Feb 2017 17:35:11 GMT

NOTE: I've also tried using api2.authorize.net instead, since a lot of the documentation seems to refer to api.authorize.net as still supported but a legacy url.

Re: CIM API requires clientID?

RichardH — Fri, 24 Feb 2017 19:34:24 GMT

Hello @kevinfairchild

ClientID is for internal use by Authorize.Net and is not required.

Richard

Re: CIM API requires clientID?

kevinfairchild — Fri, 24 Feb 2017 20:03:32 GMT

@RichardH, is something not configured correctly in the WSDL, then?

Example reference definition after refreshing web service reference:

        <System.Web.Services.Protocols.SoapDocumentMethodAttribute("https://api.authorize.net/soap/v1/CreateCustomerProfile", RequestNamespace:="https://api.authorize.net/soap/v1/", ResponseNamespace:="https://api.authorize.net/soap/v1/", Use:=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle:=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)>  _
        Public Function CreateCustomerProfile(ByVal merchantAuthentication As MerchantAuthenticationType, ByVal profile As CustomerProfileType, ByVal validationMode As ValidationModeEnum, ByVal clientId As String) As CreateCustomerProfileResponseType
            Dim results() As Object = Me.Invoke("CreateCustomerProfile", New Object() {merchantAuthentication, profile, validationMode, clientId})
            Return CType(results(0),CreateCustomerProfileResponseType)
        End Function

...thoughts?

Re: CIM API requires clientID?

Lilith — Fri, 24 Feb 2017 21:18:14 GMT

@kevinfairchild -- you mentioned compile errors that mention clientID explicitly. Could you share some examples, please?

I confirm that the WSDL has minOccurs=0, meaning the field is not mandatory, and as Richard indicated, it is an internal field only. So I'd like to see the errors to get a better idea of context.

As for the API endpoint's domain -- either api.authorize.net or api2.authorize.net should work. The difference is that api2 utilizes Akamai SureRoute for routing optimization. Both have the same WSDL and reach the same servers in the end.

(I should note we've begun to deprecate SOAP, however. While the SOAP flavor of our API will be supported, we will not be adding new features. Unless SOAP is a requirement, you may want to consider developing using the XML or JSON flavor of our API. We also have a REST API in the works, of which you'll hear more over the next several months.)

Re: CIM API requires clientID?

kevinfairchild — Fri, 24 Feb 2017 21:38:43 GMT

@Lilith,

I get a handful of them for the different create, update, delete calls done in our app.

Here's an example from the error list in VS 2015:

Error	BC30455	Argument not specified for parameter 'clientId' of 'Public Function CreateCustomerPaymentProfile(merchantAuthentication As MerchantAuthenticationType, customerProfileId As Long, paymentProfile As CustomerPaymentProfileType, validationMode As ValidationModeEnum, clientId As String) As CreateCustomerPaymentProfileResponseType'.

This problem has affected us both on a winform application as well as a ASP.NET web app.

As for SOAP being depreciated, I noticed that today as well. We'll be moving to one of the other APIs sometime this year, but until then -- we're just trying to figure out how to get around this new field requirement.

One of the other developers tried passing in an empty string, which he said seemed like it worked the first time but then failed on subsequent attempts. We have an older version of the application that doesn't have the updated API references that include that field and that seems to work correctly as-is. It's only when we update the definitions that it seems to have problems.

Re: CIM API requires clientID?

Lilith — Fri, 24 Feb 2017 21:48:42 GMT

@kevinfairchild -- as I mentioned, I reviewed the WSDL directly. No occurrence of clientId is required in an API request.

Any chance you could send us a copy of the WSDL you're using? I know you said you copied it from us, but I want to review what's cached on your server, in case something odd happened.

Re: CIM API requires clientID?

kevinfairchild — Fri, 24 Feb 2017 22:35:23 GMT

@Lilith,

Just for clarification... I have an existing winform in VS 2015 with an old reference definition for the SOAP API. No compile errors and transactions and everything work perfectly. Clicking "Update Web Reference" refreshes the definitions which then adds the new parameter and causes compile errors.

I completely agree with you that from what I can see of the WSDL, that field should not be required. I'm just reporting what is happening on seperate apps and to seperate developers after updating the reference data.

I can paste a copy of the Service.wsdl file the client has after the refresh, but I've already verified the routines I'm getting the error on all have:

<s:element minOccurs="0" maxOccurs="1" name="clientId" type="s:string" />

Seems like that's how it should be (optional) from what you've said.

I went ahead and downloaded the sample project from https://github.com/AuthorizeNet/sample-code-csharp to try to see if I could reproduce the issue with it on there, but it doesn't look like that uses a web reference to the SOAP API.

If there's anyone with a SOAP web reference in Visual Studio that can do a refresh of the definitions and let me know if they have the same issue with previously-working Authorize.Net code causing compile errors related to clientID, that would be helpful. Especially within VS 2015. At least then I'd be able to determine if it's something specific to VS 2015 or what...

Re: CIM API requires clientID?

kevinfairchild — Tue, 28 Feb 2017 20:31:40 GMT

@RichardH or @Lilith, were either of you able to do a refresh of the WSDL within VS 2015 to see if it's interpretting clientID as required?

I've had complaints of this from other developers using fresh installs of VS 2015 in different projects, so I'm wondering if that's the issue.

Re: CIM API requires clientID?

ruchi_s — Wed, 12 Apr 2017 08:01:50 GMT

Hi @kevinfairchild @Lilith @RichardH,

I am faciing the same problem. I have updated the service refence from "https://api.authorize.net/soap/v1/Service.asmx?wsdl".

Now all existing code is not working as new update added field "clientid" for most of the methods. I tried to pass loginid as clientid but disn't work.

Also, I do not have any clientid and do not want to generate this.

Please let me know the solution. I am working with Visual Studio 2012 and do not have VS 2015.

Regards

Ruchi

Re: CIM API requires clientID?

kevinfairchild — Wed, 12 Apr 2017 13:34:00 GMT

Sorry to hear you ran into the same issue, @ruchi_s. As you can see from the lack of responses on this thread, it's probably not something that will be addressed -- given their abandonment of the SOAP API.

I was unable to come up with a solution to this issue, so I'm switching to a different API.

Best of luck!

--Kevin

Re: CIM API requires clientID?

ruchi_s — Fri, 14 Apr 2017 03:49:57 GMT

Hi @kevinfairchild @RichardH ,

Will this issue be resolved if i will install visula studio 2015? Right no I am working with vs 2012.

Regards

Ruchi

Re: CIM API requires clientID?

kevinfairchild — Fri, 14 Apr 2017 13:20:14 GMT

@ruchi_s, I had the issue in both VS 2015 and VS 2017. If a project was working properly with the SOAP API, just refreshing the definition would cause it to no longer work.

To resolve the issue, I've moved on to a non-SOAP version of the API.

Good luck.

--Kevin Fairchild

Re: CIM API requires clientID?

ruchi_s — Mon, 26 Jun 2017 06:06:12 GMT

@kevinfairchild @Lilith @RichardH

Can anybody let me know what is ClientId here? I do not want to move to non-soap as i am working on a very old project and now aware of all the functionality. I just wanted to use some new api's like GetSubscription which is not available in my old service. So I need to update service but updating the service gives me problem of clientid for all existing services.

Any solution please........

Re: CIM API requires clientID?

RichardH — Mon, 26 Jun 2017 13:16:32 GMT

@ruchi_s

The Client ID is an internal value used to identify the SDK client used. If you set the value to Null, the gateway will not return an error.

RIchard

Re: CIM API requires clientID?

ruchi_s — Tue, 11 Jul 2017 07:48:07 GMT

@RichardH

Hi,

This is working fine to me now. I passed null for clientId and it worked.

Can you please let me know the reason of response "E00027 2,1,2,This transaction has been declined". On production I am trying to charge a transaction through customerprofile but transaction on AuthorizeNet are going be declined. We didn't have any rejection setting as well.

Re: CIM API requires clientID?

Aaron — Tue, 11 Jul 2017 20:08:08 GMT

Hi @ruchi_s,

That code just means the card is declined.

http://developer.authorize.net/api/reference/responseCodes.html?code=E00027.

If this is in production, it just means the cardholder's bank did not approve the transaction. If it were declined for some other reason, the text in the response would indicate a different reason. The only way to know why it was declined is to have the cardholder contact their bank.

Re: CIM API requires clientID?

ruchi_s — Wed, 12 Jul 2017 04:03:15 GMT

@Aaron @RichardH

Thanks @Aaron for quick reply. I got it.

I have a confusion regarding TLS disablement. I used TLS1.2 for sandbox and it is working fine But if I use this TLS1.2 on production it is not working. transcation on live are going to be declined on live if using TLS1.2.

Do I need to implement this exactly on 18 September? I wanted to upload my code change for TLS earlier as it way be mid of sprint on 18 september.

Re: CIM API requires clientID?

joegreentea — Wed, 12 Jul 2017 11:45:52 GMT

@ruchi_s

What kind of error that you're getting when you use TLS1.2 in live environment?

Re: CIM API requires clientID?

ruchi_s — Wed, 12 Jul 2017 12:05:44 GMT

@joegreentea

This is of Transaction declined error code E00027