Skip to content

Commit b8fe56e

Browse files
Update advanced-saml-configurations.mdx
Updates from Viv
1 parent f50a147 commit b8fe56e

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

src/content/docs/authenticate/enterprise-connections/advanced-saml-configurations.mdx

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,21 +28,21 @@ The Name ID you select in Kinde must be supported and configured in your IdP.
2828

2929
## Sign request algorithm
3030

31-
The Sign Request Algorithm defines the cryptographic algorithm used to sign SAML requests (AuthnRequest) and/or responses. Signing ensures the authenticity and integrity of SAML messages.
31+
The Sign Request Algorithm defines the cryptographic algorithm used to sign SAML requests (AuthnRequest). Signing ensures the authenticity and integrity of SAML messages.
3232

3333
Available algorithms:
3434
- **RSA-SHA256**: A commonly used and secure option.
3535
- **RSA-SHA1**: Older and less secure; often deprecated.
3636

37-
Secure configurations favor SHA256 or higher algorithms to protect against vulnerabilities.
37+
Secure configurations favor SHA256 or stronger algorithms to protect against vulnerabilities.
3838

3939
## Protocol binding
4040

4141
Protocol Binding refers to the transport mechanism used to send the SAML authentication request from Kinde to your IdP.
4242

4343
Common Binding Types:
4444
- **HTTP Redirect Binding**: The SAML request is sent as a URL parameter using a GET request. It is lightweight but limited in message size.
45-
- **HTTP POST Binding**: The SAML request is sent via an HTML form using a POST request. It supports larger payloads and is commonly used for transmitting signed requests.
45+
- **HTTP POST Binding**: The SAML request is sent via an HTML form using the POST method. It supports larger payloads and is commonly used for transmitting signed requests.
4646

4747
The choice of binding affects security, performance, and compatibility. POST Binding is generally preferred for secure communications due to its ability to handle signed messages and larger payloads.
4848

@@ -54,6 +54,7 @@ Kinde-supported key attributes:
5454

5555
- Email Address: The user’s email, often used for identification or communication.
5656
- First Name / Last Name: Used for personalization or internal system mapping.
57+
- User ID: The attribute in the SAML token that contains the user ID.
5758

5859
Only configure key attributes if supported by your IdP.
5960

0 commit comments

Comments
 (0)