/implicit/callback route not working for any version of @okta/okta-angular about okta-oidc-js HOT 5 OPEN

I am also the facing the same issue, can anyone help please..

from okta-oidc-js.

Thanks for reporting this issue, @yashwanth-yenugu. I will investigate and get back to you once I have more details on a potential root cause.

from okta-oidc-js.

@yashwanth-yenugu, I was not able to reproduce the behaviour you described in non-localhost environment
a few clarifying questions to help with further investigation:

• are you able to share the details of your OKTA_CONFIG(w/ clientId and org subdomain scratched) and the login method + parameters you are using(e.g. signInWithRedirect)?
• are there any error messages available in the non-local setup (either in URL or developer tools)?

from okta-oidc-js.

Thank you for responding .I have attached the file which contains all the details we are using to integrate with okta
agular-okat.txt

there are no error messages in the developer tools. I can see the cookies as well.

from okta-oidc-js.

thanks for following up, @yashwanth-yenugu
my next questions and suggestions:

• is accessToken still undefined when opening a new tab/doing page reload on a protected path(/providerMALogin)?
• are you making sure redirectUri origin is getting set to a proper value? (by either using environment config property or doing a shortcut like window.location.origin + '/user-manager/callback')
• did you have a chance to setup and deploy a sample app to the same environment OR would it be possible for you to try deploying your original app to a different environment? (to make sure there is no particular environment interference)

from okta-oidc-js.