How do you make clien_secret not hashed to make drf_social_oauth2 /auth/convert-token work? #248
Unanswered
slavkojovanovic
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In created a new application but I don't see the check box option for not hashing the client_secret.
This can be seen in the screen shot on this page: https://drf-social-oauth2.readthedocs.io/en/latest/application.html.
According your instructions hashed client_secret does not work with convert-token. I get the error stating this.
I do not have this option in my admin console.
![image](https://private-user-images.githubusercontent.com/44439555/362385418-d4c734d2-a383-45f0-b811-8c7bc2c00fef.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzNjMzMTAsIm5iZiI6MTczOTM2MzAxMCwicGF0aCI6Ii80NDQzOTU1NS8zNjIzODU0MTgtZDRjNzM0ZDItYTM4My00NWYwLWI4MTEtOGM3YmMyYzAwZmVmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDEyMjMzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAwZDQ1ZGYxODg1MGVmNmI1MjAwNGFhMmNiZGVmODdmNWJlOTA2OTU4ZGU2ZDU3OGY1ODc2NDM4YmNlNGJmM2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.io4k-vDu834j9z5iK9Nwk5UybZJLcgM2dqdIhfDDrBU)
How do I surface it and/or is there any workarounds.
Thank-you
Beta Was this translation helpful? Give feedback.
All reactions