We have an application using OIDC (OpenID Connect) that we are submitting for testing. The application follows the SF flow. While it is able to authenticate users in the application and handle logout successfully, it consistently fails to confirm user sign-in during testing.
All functionalities, including authentication and logout, are working fine in the application, but the issue persists with confirming user sign-in. Please refer to the images below for more details. please help
Facing the same issue, my application is built using react, I don’t even see the Test in progress dialog at all:
Submit OIN docs reference
Hi there @sodith.kumar and @Tahir52 ,
Welcome to the community!
@sodith.kumar I can’t see your images. Would you mind reattaching them, please?
Can you both post some info about your application types?
@Tahir52 , I see you mentioned React. Are you handling authentication via a back-end process or within the front-end framework?
Let’s see if we can figure this out!
Hi @alisaduncan
I couldn’t see the Test in progress dialog box to confirm that login was successful.
However I was able to fix the issue by reinstalling the okta plugin and disabling all other plugins.
Hi @Tahir52 ,
Glad to hear it’s working for you!
Hi @sodith.kumar ,
Thanks for attaching the image. I’ll reach out via DM with the next steps.
I have the same issue, my OIDC app works as expected and signs in users successfully, but it will not pass the OIN test. I’ve tried reinstalling the plugin and disabling all other plugins and have looked into what might be causing it to fail. I am stumped and need help
Hi @mpflueger if you got any solution let us also know
I definitely will, I’m having a lot of difficulty finding any public knowledge on troubleshooting this issue of the OIDC application sign on functioning successfully, but the OIN tests failing.
I have solution on our end, the issue we were facing is identified on this post from another thread: Issue with submitting to OIN: Submission Tester fails and closes a window after the auth redirect - #4 by kyleva
When navigating to our app’s login page, the app automatically sends a request to our backend authentication service to check if the user already has a valid session. If the user is not logged in, it responds with a 403 error. This error is what was causing the test to fail event though the SP sign in step was showing a green check mark (the test doesn’t show the failure until Okta sign in for some reason). I had to update the SP initiate URL to point directly to our backend auth service and bypass the frontend login (avoiding the expected 403 error). Also, as @Tahir52 has discovered, sometimes the Okta browser plugin stops working correctly and it must be removed and reinstalled. After updating the SP initiate URL to avoid the 403 error AND reinstalling the Okta browser plugin I was finally able to get the test to pass.
