Skip to content
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

[Feature Request] Support JWE (with rollover) #61

Closed
jmprieur opened this issue Mar 24, 2020 · 4 comments
Closed

[Feature Request] Support JWE (with rollover) #61

jmprieur opened this issue Mar 24, 2020 · 4 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request improved-devex scenario: improved-security

Comments

@jmprieur
Copy link
Collaborator

jmprieur commented Mar 24, 2020

Is your feature request related to a problem? Please describe.
As 1P partners move to Microsoft Identity Platform they need Ms.Id.W to support JWE, passing certificate, possibly with two certificates to support the rollover

Describe the solution you'd like

See See also https://github.com/AzureAD/microsoft-identity-web/wiki/Spec-certificates

@jmprieur jmprieur added the enhancement New feature or request label Mar 24, 2020
@abatishchev
Copy link

Hi Jean-Marc,
Yes, please! Right now JWE validation which is mandatory for 1PA is pain since one and only one certificate (registered by thumbprint) can be used.
Once it's rolled over, tokens encrypted with the previous version continue to be valid for 60 minutes.
Please prioritize the work to support a pair of certificates instead.

@jmprieur
Copy link
Collaborator Author

Thanks for the feedback @abatishchev
Currently Microsoft.Identity.Web is in alpha preview. Are you ok to use it in a 1PA ? (If you do, I'm ok to priortize the work after the work needed to make this part of the ASP.NET Core templates)

@abatishchev
Copy link

Yes, I know it's an alpha. But if it'll simplify using 1PA with JWE then we'd be happy to try it out.

@jmprieur jmprieur added the duplicate This issue or pull request already exists label Jun 10, 2020
@jmprieur
Copy link
Collaborator Author

Closing as duplicate of #165, which is in progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request improved-devex scenario: improved-security
Projects
None yet
Development

No branches or pull requests

2 participants