Users are kicked out of the lms platform after they purchase a course via authorize.net

[nitoko]

This is what happens: When a user in our client's platform purchases a course and uses authorize.net as a payment method, they get kicked out of the platform, and when they log in, the platform shows them that they have purchased the course successfully.

This is what we discovered:

We are sending the proper relay url, and authorize keeps returning the to the default one set on their side. That is why it appears that the user is not logged in, because the user is redirected to the original domain instead (the client uses a custom domain) of the custom one and he is not logged in the original one . This is a known issue I have tested by changing the Default Relay Response URL to the desired one and it works, but it will only redirect to it, and not to the one we send.

[RaynorC1emen7]

Can you duplicate the issue on your test/sandbox account?

[DoceboHelp]

Yes. This issue has been occurring for 5 months and we have yet to make any headway with Authorize. Prior to the updates made to your Response URL this issue was not occurring. The clients default response URL and additional response URL are properly defined.

[RaynorC1emen7]

So it the same issus as the OP where it work if it go to the default relay response url but not when it passing in as param?

[DoceboHelp]

We are all working to resolve the issues of a Docebo client.

"This is what happens: When a user in our client's platform purchases a course and uses authorize.net as a payment method, they get kicked out of the platform, and when they log in, the platform shows them that they have purchased the course successfully.

This is what we discovered:

We are sending the proper relay url, and authorize keeps returning the to the default one set on their side. That is why it appears that the user is not logged in, because the user is redirected to the original domain instead (the client uses a custom domain) of the custom one and he is not logged in the original one . This is a known issue I have tested by changing the Default Relay Response URL to the desired one and it works, but it will only redirect to it, and not to the one we send."

[RichardH]

Hello @DoceboHelp

From your description, the transaction is completing successfully, but the relay response is not.

It would really help to have more specifics for each of the elements:

• Are you using a whitelist to block access?  See this post for our server IP addresses.
• What is the full URL with parameters configured in your relay response?  We'll examine it for length, URL encoding, supported characters, etc.
• Could you specifythe "original" and "custom" domain urls?

Richard

[DoceboHelp]

Are you using a whitelist to block access?

---No

What is the full URL with parameters configured in your relay response?  We'll examine it for length, URL encoding, supported characters, etc.

---(https://congauniversity.docebosaas.com/lms/index.php?r=cart/authnetRelayResponse - original domain ,https://congau.congasphere.com/lms/index.php?r=cart/authnetRelayResponse - custom domain )

Could you specify the "original" and "custom" domain urls?

--- (https://congauniversity.docebosaas.com -original ,
https://congau.congasphere.com - custom )

[RichardH]

Hello @DoceboHelp

We don't recommend using parameterized URLs.  That said, you might try URL encoding the slash in your parameter and see if that works.   https://congau.congasphere.com/lms/index.php?r=cart%2fauthnetRelayResponse

Richard

[DoceboHelp]

Checking with the client. Thank you for the suggestion.

~Docebo Support