You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi all,
Im using go-oidc for a while now, where Azure AD is the IDP.
lately Azure having issues once in a while in returning the well-known config file in the Provider GET request.
this causing timeout in my software and that is messy .
I wonder if the package have some kind of caching for that purpose and i didn't see it ,
Amir
The text was updated successfully, but these errors were encountered:
The suggested pattern of this program is to use NewProvider() once, construct a long lived IDTokenVerifier then use that to verify tokens. In that case, you "cache" the discovery data manually.
hi all,
Im using go-oidc for a while now, where Azure AD is the IDP.
lately Azure having issues once in a while in returning the well-known config file in the Provider GET request.
this causing timeout in my software and that is messy .
I wonder if the package have some kind of caching for that purpose and i didn't see it ,
Amir
The text was updated successfully, but these errors were encountered: