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
{{ message }}
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.
Access token validation is done by a resource server, and it likely will not know the client_id of the client making the request ahead of time, such as when an API is used by an arbitrary number of OAuth clients in an organization. As such, it shouldn't be required to configure the library with a client_id before validating a token.
The Okta .NET and Java SDKs also don't require setting a client_id in order to use the JWT verifier library, so this should match those libraries as well.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Access token validation is done by a resource server, and it likely will not know the
client_id
of the client making the request ahead of time, such as when an API is used by an arbitrary number of OAuth clients in an organization. As such, it shouldn't be required to configure the library with aclient_id
before validating a token.The Okta .NET and Java SDKs also don't require setting a
client_id
in order to use the JWT verifier library, so this should match those libraries as well.The text was updated successfully, but these errors were encountered: