<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
0D54z00009jnv0rCAAOkta Classic EngineSingle Sign-OnAnswered2025-09-13T09:01:51.000Z2023-10-09T12:57:23.000Z2023-10-31T21:59:16.000Z

AishwaryaB.58028 (Customer) asked a question.

When using a direct link the Okta App functions correctly despite encountering an unknown authentication strategy SAML in other scenarios

We have OKTA based SSO integration in our system. This integration is working fine for over a year now. Recently we have started encountering an intermittent issue while logging in from inside the Okta app dashboard to our app. When we try to authenticate the session using passport js. Passport js throws this error Error Unknown authentication strategy saml. If the user is directly logging in from our admin panel url, then the user is redirected to OKTA and flow works fine.

 

Steps to reproduce

 

Create the new app by logging into the admin user.

 

Pass all configurations in the app.

 

Assign the app to the user.

 

Click on the finish button.

 

Now login from the above user.

 

Click on the newly created app, User should be able to access our app, but its throwing above error intermittently


  • Hi @AishwaryaB.58028 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

     This question is more appropriate for our dedicated Okta Developer Forum.

    My advice would be to reach out devforum.okta.com to take advantage of their expertise.  

    While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work). 

     

    That being said, I've looked into this and was able to find just one other similar report which was determined to be a non-Okta issue.  

    I can't share all the details of the case were this was reported but I can share the following customer response which may or may not provide value for your use case.  

    " The 500 error I get is because passport (I'm using passport version 0.6.0) returns when the last step is to parse the SAML response from XML, it's always empty object, with the same codebase, other Apps I always get SAML response XML and parse data (firstName, lastName, email, login, trusted) "

     

    If above does not help with your situation, please feel free to reach out to my developer colleagues on devforum.okta.com.  

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Expand Post
    Selected as Best
  • Hi @AishwaryaB.58028 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

     This question is more appropriate for our dedicated Okta Developer Forum.

    My advice would be to reach out devforum.okta.com to take advantage of their expertise.  

    While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work). 

     

    That being said, I've looked into this and was able to find just one other similar report which was determined to be a non-Okta issue.  

    I can't share all the details of the case were this was reported but I can share the following customer response which may or may not provide value for your use case.  

    " The 500 error I get is because passport (I'm using passport version 0.6.0) returns when the last step is to parse the SAML response from XML, it's always empty object, with the same codebase, other Apps I always get SAML response XML and parse data (firstName, lastName, email, login, trusted) "

     

    If above does not help with your situation, please feel free to reach out to my developer colleagues on devforum.okta.com.  

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Expand Post
    Selected as Best
  • a0n5s (a0n5s)

    @AishwaryaB.58028 (Customer)​ you can try install the SAML trace plugin in chrome and try again. then check the flow in saml trace and find what happened.

This question is closed.
Loading
When using a direct link the Okta App functions correctly despite encountering an unknown authentication strategy SAML in other scenarios