-
Notifications
You must be signed in to change notification settings - Fork 82
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* adding saml-attributestatement.md * adding attribute-statement.png * restructure doc * typo fixes * fixed image link * edit doc * fix errors re: IdP and SP --------- Co-authored-by: Sara Santillan <[email protected]> Co-authored-by: Katie Horne <[email protected]>
- Loading branch information
1 parent
cbad51a
commit 2b232ef
Showing
2 changed files
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
description: Fix a SAML configuration error when an AttributeStatement is missing. | ||
tags: | ||
- Semgrep Cloud Platform | ||
- SSO | ||
- Troubleshooting | ||
--- | ||
|
||
import MoreHelp from "/src/components/MoreHelp" | ||
|
||
# SAML configuration error: There is no AttributeStatement on the Response | ||
|
||
When configuring SAML single sign-on (SSO) in Semgrep Cloud Platform, you may encounter the following error: `There is no AttributeStatement on the Response` | ||
|
||
![SAML AttributeStatement error](/img/attribute-statement.png#md-width) | ||
|
||
This error occurs when [an attribute within the SAML response does not contain a value](https://support.okta.com/help/s/article/SAML-attribute-statement-with-no-value-configured-not-properly-closed-in-assertion?language=en_US), resulting in a SAML assertion that does not correctly close the attribute statement. The attribute statement causes an SSO error when the service provider (SP) receives the SAML response. | ||
|
||
## Find the SAML attribute that is causing the error | ||
|
||
1. If you do not know the attribute that is causing the error, you can [identify it by investigating the payload](https://support.okta.com/help/s/article/How-to-View-a-SAML-Response-in-Your-Browser-for-Troubleshooting?language=en_US). | ||
|
||
2. Once you have identified the attribute in question, there are two ways for you to fix the issue. The best option depends on what information your SP expects to receive: | ||
|
||
- If your SP anticipates a value for the specific SAML attribute statement, you must add the value within your SAML settings. When [setting up SSO to Semgrep Cloud Platform](/semgrep-cloud-platform/sso/#saml-20), you must provide `name` and `email`. | ||
- If your SP does *not* expect the attribute statement in your SAML settings, you can remove it. | ||
|
||
Regardless of which option you choose, you can update or remove SAML attribute statements with your identity provider (IdP); check with your IdP for instructions on how to do so. | ||
|
||
<MoreHelp /> |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.