forked from mystiq/dex
8b8c076ecf
Now that LDAP supports an `insecureSkipVerify` option, clarify that `insecureNoTLS` is an extremely bad choice and as such we may drop support for 389 in the future. However, since we send plain text passwords from our frontend to our backend, this probably gets us into a bigger conversation about dex's TLS story. For example when terminiation is approporate. cc'ing @dghubble for thoughts on how that might apply to our internal uses. We probably want an overaching security doc at some point, but that can be another PR. |
||
|---|---|---|
| .. | ||
| img | ||
| logos | ||
| proposals | ||
| api.md | ||
| dev-integration-tests.md | ||
| dev-releases.md | ||
| getting-started.md | ||
| github-connector.md | ||
| kubernetes.md | ||
| ldap-connector.md | ||
| openid-connect.md | ||
| storage.md | ||
| v2.md | ||