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
Don't treat Application.client_secret as encrypted
In newer DOT than what AWX uses, Application.client_secret is hashed
automatically with no way to disable that functionality.
There's a PR that allows for disabling that functionality ([0]), but
that hasn't made it into a release.
The DOT hashing is incompatible with our standard encryption - when
DOT gets the value it ends up getting our encrypted string and trying
to act on that. Ideally we'd like to disable their hashing entirely
and use our standard encryption tooling.
AWX avoids this problem by pinning to an older DOT.
For now in DAB we'll just use the upstream hashing, and not treat the
field as an encrypted_fields field to avoid the "double encryption"
issue.
[0]: django-oauth/django-oauth-toolkit#1311
Signed-off-by: Rick Elrod <[email protected]>
field=oauth2_provider.models.ClientSecretField(blank=True, db_index=True, default=oauth2_provider.generators.generate_client_secret, help_text='Hashed on Save. Copy it now if this is a new secret.', max_length=255),
0 commit comments