Thank you both for your explanations, it helped me to solve my problem but i’m not sure I’m on the right Authorization Server.
@vijet You were right, I had a misconfiguration server side, for a working authentication I had to use the IdToken and not the access_token then change the configuration as following:
Client Side Issuer: ‘https://{myOktaDomain}.com’
Server Side Issuer: ‘https://{myOktaDomain}.com/oauth2/’
Server Side Audience: My Client Side app clientId
If I try to use https://{myOktaDomain}.com/oauth2/default as issuer client side, i’m not redirected to the Okta login page and I get an angular-oauth2-oidc uncaught error.
Maybe it’s due to my app configuration in Okta (See screenshots of my configuration at the end of the post)
@tom When I say that i’m using the Okta authentification on the client side I mean that I use the package angular-oauth2-oidc who redirect to the default Okta login page on login then get back app on success via the redirect uri. (I don’t use on okta widget or custom login form on my web app).
The issuer for my access token and my Id token is: https://{myOktaDomain}.com
For the Id Token the audience is my ap clientId and for the Access Token it is the same url as the issuer.
Thank you again.!
