SCIM Integration - Okta callback gets 503 error

[ktelant]

I found several posts with similar issue but I don’t see a straight answer. Sorry I have to ask it again.

I’m trying to provison SCIM integration with a SAP Commerce (Hybris) application which has an OAuth2 server too.

• I created a OAuth2 client in the SAP Commerce.
• Then in Okta SCIM integration, I filled out all the required information.Clicked on the button “Authenticate with {APPNAME}”.
• A new browser window directed me to the OAuth2 server. After login successfully, the browser window redirects to GET https://system-admin.okta.com/admin/app/cpc/dev-17947277_dcbackofficelocaltest_1/oauth/callback?code=XXXXXX&state=YYYYYY. The response is 302.
• Then then the browser window redirects to https://dev-17947277-admin.okta.com/admin/app/cpc/dev-17947277_dcbackofficelocaltest_1/ZZZZZZ/oauth/callback?code=XXXXXX&state=YYYYYY, here I got the 503 error.

It seems to me that it will be something to be done at Okta side. Does anyone know what it could be? Thanks a million!

[andrea]

In checking our logs, it seems like the token endpoint configured for this integration is hosted locally (https://*****.local:9002) so we did not make the request.

Is your OAuth server and its associated endpoints not available publicly?

[ktelant]

Andrea,

Thank you for checking it back. Yes. It is a test environment. I thought every request/response is handled by URL redirecting, so the web browser is always initiating the transaction. If it is not the case and the 503 error is the result that Okta cannot connect to the localhost, we have some environments that are accessible publicly and have the same issue. I will collect some information from those environment and post it here. Thank you!

[andrea]

Yeah, the /token request is going to be a backend POST call, so it will need to be publicly available.