Open
Conversation
memurats
added
custom
memurats
force-pushed
the
nmc/33/785-telekom-bearer-secret
branch
from
e2d9cf9 to
e2d1beb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Telekom bearer token handling requires a secret different from the OpenID Connect client secret.
Field is added with the following properties:
delivered as plain text, but internal token handling requires base64 encoding, so the field is base64 encoded/decoded internally
the secret is encrypted in the same way as all other secret information in user_oidc.
we keep the old DB migration sequence from NMC V24
this PR only contains the DB and command line changes.