Update exchange_key description to use different HMAC setting (#5909)

* Update exchange_key description to use different HMAC setting

Signed-off-by: John Heraghty <148883955+john-eliatra@users.noreply.github.com>

* Update _security/authentication-backends/saml.md

Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Signed-off-by: John Heraghty <148883955+john-eliatra@users.noreply.github.com>

* Update saml.md

Signed-off-by: John Heraghty <148883955+john-eliatra@users.noreply.github.com>

* Update saml.md

Update to the exchange key description to give more of an instruction to the user on what to enter there.

Signed-off-by: John Heraghty <148883955+john-eliatra@users.noreply.github.com>

* Update _security/authentication-backends/saml.md

Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>

---------

Signed-off-by: John Heraghty <148883955+john-eliatra@users.noreply.github.com>
Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
This commit is contained in:
John Heraghty 2024-02-01 17:48:17 +00:00 committed by GitHub
parent 44aebde47a
commit 8224d69c1b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions

View File

@ -224,7 +224,8 @@ SAML, unlike other protocols, is not meant to be used for exchanging user creden
Name | Description
:--- | :---
`exchange_key` | The key to sign the token. The algorithm is HMAC-SHA512, so it should have at least 64 characters, and base64 URL encoding.
`exchange_key` | The key to sign the token. The algorithm is HMACSHA512, therefore we recommend to use 64 characters, for example `9a2h8ajasdfhsdiydfn7dtd6d5ashsd89a2h8ajasdHhsdiyLfn7dtd6d5ashsdI`. Ensure that you enter a value for `exchange_key`, otherwise an error is returned.
## TLS settings