-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update LMS private key JWKs to prepare for pyjwkest removal #261
Comments
@rgraber may be able to help @timmc-edx as eSRE. |
Yes, I can do this. I ran it by SRE just to be sure and they told me to go for it. |
@timmc-edx am I correct in assuming I should also do this for sandboxes? |
We have decided to update the key rather than roll it since it requires less e/SRE intervention. This is blocked on getting the decrypted private key from SRE, who have it in their sprint. |
Follow up ticket for updating generate_jwt_signing_key is openedx/edx-platform#32125 . Sandboxes use this to generate keys on provisioning, so updating the script should update sandboxes as well. |
As part of openedx/edx-drf-extensions#290 we need to update our JWKs to be forward-compatible with PyJWT, which requires that either all optional params are present in an RSA JWK, or none are. (With pyjwkest, we've been able to get away with having a partial list of these precomputed values.)
In openedx/edx-platform#31927 we determined that the likely least-friction method of upgrading is to update the private keys in-place to include all of the precomputed private numbers:
generate_jwt_signing_key
to produce keys with all optional params includedThe text was updated successfully, but these errors were encountered: