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
Use an RFC8628 compliant client, or just set your client-secret in your client to an empty string.
Additional Information
Dex does have the ability to use "public: true" on clients, which restricts some activity. However, there should be no need to include client secret credentials in clients, so if somebody does not know that they need to configure their client as public, they could end up leaking credentials.
The only reason to tangible security reason to include the secret is if somebody is using Device Flow in a situation where their secret is actually secret. But in that case, they have no reason to be using this flow in the first place.
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Expected Behavior
When handling a Device Authorization Grant, a RFC8628-compliant client will not send the client secret.
Actual Behavior
If you don't provide a secret, you get an "Invalid client credentials" error. See server/deviceflowhandlers.go#L74.
Steps To Reproduce
Use an RFC8628 compliant client, or just set your client-secret in your client to an empty string.
Additional Information
Dex does have the ability to use "public: true" on clients, which restricts some activity. However, there should be no need to include client secret credentials in clients, so if somebody does not know that they need to configure their client as public, they could end up leaking credentials.
The only reason to tangible security reason to include the secret is if somebody is using Device Flow in a situation where their secret is actually secret. But in that case, they have no reason to be using this flow in the first place.
The text was updated successfully, but these errors were encountered: