-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSAL Interceptor unable to find cached token issued from custom OIDC server #6046
Comments
@alamfsmb Can you please share Trace level MSAL logs so we can help you debug? It's worth also mentioning that we do not have explicit support for any 3rd party identity providers. We'll do our best to unblock you by pointing you in the right direction but if fixes are needed on MSAL they're unlikely to be prioritized, it would likely fall on you to open a pull request with the changes. Just FYI. |
Appreciate you taking a look for us! We understand there isn't official support, but hope we can still take advantage of this library. I've attached the logs generated after initiating the API call matching with our configured protectedResourceMap. We don't have custom scopes so I just included the default scopes in the configuration.
|
@alamfsmb Thanks, can you email me the contents of localStorage? Please remove the "secret" field from the access and refresh token entries before sending. |
I'm thinking this may be due to the uppercase 'A' in your clientId. It looks like our credential filters are not normalizing case, which is a bug on us. Can you try with an all lowercase clientId and see if that works? If you can confirm, I'll mark this as a bug and add it to our backlog. |
@tnorling Oh that is a good thought - I didn't consider that, but unfortunately it did not resolve it trying just now, and I had an all lowercase clientId before sending this example too. I think it is failing on the matchEnvironment filter because the trace doesn't output |
One other thing I'm noticing is that your knownAuthorities array has |
I should've tried that first, my apologies! The issue was just not defining the jwks_uri in the authorityMetadata. Thanks for all your help! |
Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.37.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.5.7
Public or Confidential Client?
Public
Description
We are trying to use the MSAL angular library in
OIDC
protocol mode with a custom OIDC server but having trouble using the MSAL interceptor.Shortly after logging in, when I trigger an HTTP request that activates the MSAL interceptor, the trace logs show that acquireTokenSilent is rejected and it tries to acquire by redirect, but this happens every time the interceptor is activated and the HTTP request is never actually made. Not sure if it is a problem with our implementation client side or maybe if the OIDC server is not compliant. I can see all the tokens in local storage, but the interceptor seems to not capture them and I think it may relate to failure to check the authority meta data.
MSAL Configuration
Relevant Code Snippets
The text was updated successfully, but these errors were encountered: