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

Authorization Server should have single key configuration to match Resource Server #56

Closed
jzheaux opened this Issue Oct 22, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@jzheaux
Contributor

jzheaux commented Oct 22, 2018

Resource Server can conveniently be configured to supply a single public key for verifying JWT tokens:

security.oauth2.resource.jwt.key-value=${PUBLIC_KEY}

And it's confusing that the same functionality is not afforded on the Authorization Server.

Let's introduce the ability to supply the associated private key on the Authorization Server:

security.oauth2.authorization.jwt.key-value=${PRIVATE_KEY}

@jzheaux jzheaux added the enhancement label Oct 22, 2018

@jzheaux jzheaux added this to the 2.1.0.RC1 milestone Oct 22, 2018

@jzheaux jzheaux self-assigned this Oct 22, 2018

@jzheaux jzheaux closed this in e36fd87 Oct 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment