mirror of
https://github.com/kanidm/kanidm.git
synced 2025-04-25 11:45:39 +02:00
Compare commits
2 commits
dad04058c6
...
7fc797822f
Author | SHA1 | Date | |
---|---|---|---|
|
7fc797822f | ||
|
cc9433fbd4 |
|
@ -52,6 +52,19 @@ configured.
|
|||
Similarly, WebAuthn and its various other names like Passkeys, FIDO2 or "scan the QR code to log in"
|
||||
will [only work over TLS](https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API).
|
||||
|
||||
There are a variety of ways that you can configure TLS between your load balancer and Kanidm.
|
||||
Ultimately, any option that maintains the confidentiality and integrity of the communication will
|
||||
suffice. Some options include, but are not limited to:
|
||||
|
||||
- Generating a self-signed certificate
|
||||
- Utilize certificate pinning to ensure that the load balancer only trusts connections made with
|
||||
that particular certificate
|
||||
- Not terminating TLS / TLS passthrough / TCP proxy
|
||||
- Running your own certificate authority (CA)
|
||||
|
||||
The "best" option for you will depend on a number of factors, including your threat model and the
|
||||
specifc load balancer you are using.
|
||||
|
||||
## OAuth2
|
||||
|
||||
[RFC6819 - OAuth2 Threat Model and Security Considerations](https://www.rfc-editor.org/rfc/rfc6819)
|
||||
|
|
Loading…
Reference in a new issue