Expand my Community achievements bar.

SOLVED

AEM OKTA : Okta login page where a spinner appears indefinitely

Avatar

Level 1

Hi Everyone,

In the context of the AEM (Adobe Experience Manager) integration with Okta, if you are encountering a situation where the OKTA login page displays an endless spinner, I would appreciate any insights or suggestions you may have based on your prior experience with similar errors. Please share your thoughts and ideas on how to address this issue effectively.

 

Sateesh583_0-1706490627351.png

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@Sateesh583 ,

Try configuring the CORS Policy OSGI configuration on the server where the OKTA authentication is happening.
https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/security/understand-cros...

 

Allowed Origin value should be your OKTA IDP domain name.

 

 

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

@Sateesh583 ,

Try configuring the CORS Policy OSGI configuration on the server where the OKTA authentication is happening.
https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/security/understand-cros...

 

Allowed Origin value should be your OKTA IDP domain name.

 

 

Avatar

Administrator

@Sateesh583 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni

Avatar

Level 1

Thank you for your all inputs @kautuk_sahni  @Sudheer_Sundalam @arunpatidar . 

 

The issue resides with the CORS configuration after adding the below configuration the OKTA infinite spinner is resolved. 

 

Config:  com.adobe.granite.cors.impl.CORSPolicyImpl~wknd.cfg.json

{
"alloworigin": ["null","https://dev-92XXXXX-admin.okta.com"],
"allowedpaths": [
".*/content/wknd/us/en/saml_login"
],
"supportedheaders": [
"Authorization",
"Origin",
"Accept",
"X-Requested-With",
"Content-Type",
"Access-Control-Request-Method",
"Access-Control-Request-Headers"
],
"alloworiginregexp": [],
"supportedmethods": [
"POST"
]
}
 
Among all these main property is "Authorization" for this spinner issue. 
 
Thank you all ...
Sateesh Anasani.