-
Notifications
You must be signed in to change notification settings - Fork 638
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
support both X509Certificate and JsonWebKeySet at the same time #1000
Comments
stevehu
added a commit
that referenced
this issue
Jul 14, 2021
stevehu
added a commit
that referenced
this issue
Jul 14, 2021
stevehu
added a commit
that referenced
this issue
Jul 14, 2021
younggwon1
pushed a commit
to younggwon1/light-4j
that referenced
this issue
Feb 10, 2024
…t the same time (networknt#1001)
younggwon1
pushed a commit
to younggwon1/light-4j
that referenced
this issue
Feb 10, 2024
younggwon1
pushed a commit
to younggwon1/light-4j
that referenced
this issue
Feb 10, 2024
… to go with JWK
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the current security implementation, the user can choose X509Certificate or JsonWebKeySet. When we offer the http-sidecar, some customers want to manage the business endpoints with their OAuth 2.0 provider and admin endpoints with light-oauth2 or oauth-kafka. The admin endpoints will be used by the light-controller/light-portal to access the sidecar and they can be secured with a separate OAuth 2.0 provider.
The text was updated successfully, but these errors were encountered: