You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output of deck gateway dump leaves out the secret and makes it impossible to sync without modification.
Ideally, deck would not require secret at all for RS256 (and whatever others don't require it) so that dummy values are not required, and the diff/sync functionality works correctly.
EDIT: apologies for the edit. I was partially mistaken with my original issue description -- deck gateway diff and deck gateway sync do seem to correctly ignore the "dummy" secret so that it doesn't force an update.
The text was updated successfully, but these errors were encountered:
ffjeremy
changed the title
deck sync and diff always see a change for RS256 JWT consumer secrets
deck gateway dump with RS256 JWT consumer secrets cannot be synced
Feb 22, 2024
ffjeremy
changed the title
deck gateway dump with RS256 JWT consumer secrets cannot be synced
deck gateway dump with RS256 JWT consumer secrets cannot be synced without modification
Feb 22, 2024
This was discussed here previously.
The output of
deck gateway dump
leaves out thesecret
and makes it impossible to sync without modification.Ideally, deck would not require
secret
at all for RS256 (and whatever others don't require it) so that dummy values are not required, and the diff/sync functionality works correctly.EDIT: apologies for the edit. I was partially mistaken with my original issue description --
deck gateway diff
anddeck gateway sync
do seem to correctly ignore the "dummy" secret so that it doesn't force an update.The text was updated successfully, but these errors were encountered: