-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy using TLS unless --no-tls
flag is set
#2
Labels
Comments
Comment by bcwaldon Removing this for now as our use case does not require native TLS |
kpschuck
pushed a commit
to kpschuck/dex
that referenced
this issue
Jul 10, 2018
Ldap group unit testing with travis
wolfeidau
pushed a commit
to wolfeidau/dex
that referenced
this issue
Mar 14, 2020
* Added /device/token handler with associated business logic and storage tests. Perform user code exchange, flag the device code as complete. Moved device handler code into its own file for cleanliness. Cleanup * Removed PKCE code * Rate limiting for /device/token endpoint based on ietf standards * Configurable Device expiry
JoelSpeed
pushed a commit
that referenced
this issue
Aug 28, 2020
* Added /device/token handler with associated business logic and storage tests. Perform user code exchange, flag the device code as complete. Moved device handler code into its own file for cleanliness. Cleanup * Removed PKCE code * Rate limiting for /device/token endpoint based on ietf standards * Configurable Device expiry Signed-off-by: justin-slowik <justin.slowik@thermofisher.com>
rene-dekker
referenced
this issue
in rene-dekker/dex
Jul 25, 2022
* feat(web): porting calico web branding * feat(Makefile): add tag for image * fix(Makefile): using extra tags var
1 task
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue by bcwaldon
Tuesday Nov 11, 2014 at 21:16 GMT
Originally opened as https://github.com/coreos-inc/auth/issues/26
TLS is absolutely necessary to protect the transmission of client secrets. However, there are two primary use-cases for not deploying authd with TLS:
Together, these use-cases add an interesting requirement: the ability to advertise HTTP vs HTTPS in the ProviderConfig. If TLS is completely off (the development use-case), then the ProviderConfig should advertise its endpoints using HTTP. If TLS is in use between clients and the load balancer, the ProviderConfig should still advertise HTTPS, but authd actually has nothing to do with TLS.
The text was updated successfully, but these errors were encountered: