<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009LeR5ECAVOkta Classic EngineIntegrationsAnswered2023-06-16T23:13:16.000Z2023-06-16T07:44:33.000Z2023-06-16T23:13:16.000Z
SAML REDIRECT ISSUE

We have integrated OKTA SAML in a application which uses Angular JS as client and Springboot as server. We have integrated and deployed the same app in a test and stage environment which uses https and http protocol respectively where frontend is deployed in NGINX and backend in deployed in JBOSS and the application is working fine in both environments. Now, when we tried to do the same in a preprod server which uses https protocol. We were able to login but after logging in, we were met with the following exception,

 

2023-06-15 01:18:19,865 ERROR [org.opensaml.common.binding.decoding.BaseSAMLMessageDecoder] (default task-10) SAML message intended destination endpoint 'https://xxxx/lead/api/saml/SSO' did not match the recipient endpoint 'http://xxxx/lead/api/saml/SSO'

 

We have used https in all the places where we use the URL but not sure where the http is configured !


This question is closed.
Loading
SAML REDIRECT ISSUE