-
Notifications
You must be signed in to change notification settings - Fork 329
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] Implement POP (SHR) for confidential client bringing your own keys (#2) #2013
Comments
Continuation of #1946 |
Closed
@trwalke do we need to do more ? |
@jmprieur - the second deliverable is around exposing an interface that enables users to bring their own POP keys. |
Merged
Blocked on spec. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What MSAL implements today:
IPoPCryptoProvider
for key managementTasks to complete:
First deliverable
Second deliverable
IPoPCryptoProvider
interface to provide a higher level abstraction. The currentCannonicalPublicKeyJwk
is pretty low level. Or maybe it's ok as Wilson can plugin here.WithProofOfPossession
that takes in aIPoPCryptoProvider
so that customers can define their own key management.The text was updated successfully, but these errors were encountered: