-
Notifications
You must be signed in to change notification settings - Fork 33
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
fix(JWTManager): Mark private key as sensitive #801
fix(JWTManager): Mark private key as sensitive #801
Conversation
Signed-off-by: provokateurin <[email protected]>
@@ -44,6 +44,7 @@ More information is available in the External sites documentation.]]></descripti | |||
<repair-steps> | |||
<post-migration> | |||
<step>OCA\External\Migration\CopyDefaultIcons</step> | |||
<step>OCA\External\Migration\JWTTokenPrivateKeySensitive</step> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So you're going to run this on each upgrade. Don't you wanna run it only once?
I did that in a migration step in a bunch of apps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Abusing the database migrations to do this feels wrong to me.
Executing this repair step is extremely cheap, so I think this is fine.
/backport to stable30 |
/backport to stable29 |
/backport to stable28 |
No description provided.