Documentation Index
Fetch the complete documentation index at: https://docs.semgrep.dev/llms.txt
Use this file to discover all available pages before exploring further.
YOUR DEPLOYMENT JOURNEY
- You have gained the necessary resource access and permissions required for deployment.
- You have created a Semgrep account and organization.
- You are an admin for both your Semgrep deployment and your IdP provider.
- For GitHub and GitLab users: You have connected your source code manager.
- Guided setup (beta)
- Legacy manual configuration
OpenID Connect / OAuth 2.0
MICROSOFT ENTRA IDSemgrep AppSec Platform does not support using OpenID with Microsoft Entra ID. Follow the instructions to set up SAML SSO with Microsoft Entra ID instead.
Sign in to Semgrep AppSec Platform.
The Configure Single Sign-On dialog appears. Begin by selecting your identity provider, or choose Custom OIDC.
Follow the instructions provided on the subsequent Configure Single Sign-On dialog pages to complete this process. When you’ve completed the required steps, use Test sign-in to test the connection.
Once test sign-in has passed, close the test page. Verify that the Connection details shown on the Connection activated screen are correct and close the dialog.
Verify that the Connection status is now active under the Single sign-on (SSO) section in Semgrep AppSec Platform.
SAML 2.0
GOOGLE WORKSPACE SAMLIf you’re using Google Workspace SAML, see SAML Single Sign-on with Google Workspace for specific guidance.
Sign in to Semgrep AppSec Platform.
The Configure Single Sign-On dialog appears to guide you through the remaining configuration steps. Begin by selecting your identity provider, or choose Custom SAML.
Follow the instructions provided on the subsequent Configure Single Sign-On dialog pages to complete this process. If prompted, add in the requested attribute statements. Semgrep recommends the following mappings:
| Name | Value |
|---|---|
| id | user.login OR user.email |
user.email | |
| firstName | user.firstName |
| lastName | user.lastName |
| When you’ve completed the required steps, use Test sign-in to test the connection. |
Once test sign-in has passed, close the test page. Verify that the Connection details shown on the Connection activated screen are correct and close the dialog.
Verify that the Connection status is now active under the Single sign-on (SSO) section in Semgrep AppSec Platform.
ADMIN AND ORG OWNER ACCOUNTSBy default, Semgrep creates new SSO accounts with the Member role assigned. You can change the default role assigned to a new user by going to Settings > Access.If you’re an admin setting up SSO, and Semgrep creates an SSO account for you with the role of Member, you can elevate the permissions granted to your SSO account. To do so, log in to Semgrep with your admin account using the original login method, then change the role of your newly created SSO account to Admin.
Turn off sign in with GitHub / GitLab
If you have SSO enabled, you can turn off login using GitHub or GitLab credentials. Doing so forces members of your organization to log in using an email address with an approved domain.Sign in to your Semgrep account.
Navigate to Settings > Access > Login methods.






