Retrieve the identity management configuration for your environment.
Use this endpoint to get the current identity management settings configured in your environment.
Frontegg offers a comprehensive suite of authentication, user management, and security features to streamline identity management and enhance application security. This section provides an overview of all relevant API endpoints, organized into Authentication, Management, and Self-Service categories.
Authentication Endpoints: Enable secure user login, multi-factor authentication (MFA), passwordless options, and social login integrations, allowing for a flexible and robust sign-in experience.
Management Endpoints: Require environment-level authorization and provide full control over SSO (SAML and OpenID Connect) resources, user roles, permissions, and configurations. These endpoints are designed for administrative use, allowing for centralized identity and access management.
Self-Service Endpoints: Accessible with a user token (JWT), these endpoints empower users to manage their SSO connections and other account settings. Users with the necessary permissions can create, update, or delete SSO configurations directly, ensuring they have the tools to manage their access securely and independently.
Each category in this section helps you configure and extend Frontegg’s capabilities, providing the flexibility to manage user identities, authentication protocols, and access controls as per your application’s needs.
Update the identity management configuration for your environment.
Use this endpoint to add or update identity management parameters by sending the desired values in the request body.
Refer to the parameter documentation for the list of supported values.
Security warning: Setting addPermissionsToJwt to false removes permission claims from the issued JWT. If your API routes rely on those claims for permission-based authorization, they may no longer be protected, and a user with no permissions could gain admin-equivalent read and write access. Only disable it if you enforce authorization by another means.
Controls whether permission claims are included in the issued JWT. When true, the user's permissions are added to the token.
Security warning: Setting this to false removes the permission claims from the issued JWT. If your API routes rely on those claims for permission-based authorization, they may no longer be protected, and a user with no permissions could gain admin-equivalent read and write access. Only disable this if you enforce authorization by another means.
curl -i -X POST \
https://api.frontegg.com/identity/resources/configurations/v1 \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"defaultTokenExpiration": 10,
"defaultRefreshTokenExpiration": 15552000,
"cookieSameSite": "STRICT",
"machineToMachineAuthStrategy": "ClientCredentials",
"allowSignups": true,
"apiTokensEnabled": true,
"allowOverridePasswordComplexity": true,
"allowOverridePasswordExpiration": true,
"allowOverrideEnforcePasswordHistory": true,
"jwtAlgorithm": "HS256",
"allowNotVerifiedUsersLogin": true,
"forcePermissions": true,
"addSamlAttributesToJwt": true,
"authStrategy": "Code",
"defaultPasswordlessTokenExpiration": 0,
"forceSameDeviceOnAuth": true,
"allowTenantInvitations": true,
"rotateRefreshTokens": true,
"skipTenantValidation": true,
"addRolesToJwt": true,
"addPermissionsToJwt": true,
"allowCustomLoginTenantSwitch": true
}'{ "id": "string", "defaultTokenExpiration": 0, "defaultRefreshTokenExpiration": 0, "publicKey": "string", "cookieSameSite": "STRICT", "allowSignups": true, "apiTokensEnabled": true, "allowOverridePasswordComplexity": true, "allowOverridePasswordExpiration": true, "allowOverrideEnforcePasswordHistory": true, "jwtAlgorithm": "RS256", "jwtSecret": "string", "allowNotVerifiedUsersLogin": true, "forcePermissions": true, "authStrategy": "EmailAndPassword", "defaultPasswordlessTokenExpiration": 0, "forceSameDeviceOnAuth": true, "allowTenantInvitations": true, "rotateRefreshTokens": true, "machineToMachineAuthStrategy": "ClientCredentials", "addRolesToJwt": true, "addPermissionsToJwt": true, "refreshTokensRotationLimit": 0, "addSamlAttributesToJwt": true, "allowCustomLoginTenantSwitch": true }
curl -i -X GET \
https://api.frontegg.com/identity/resources/configurations/v1 \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "id": "string", "defaultTokenExpiration": 0, "defaultRefreshTokenExpiration": 0, "publicKey": "string", "cookieSameSite": "STRICT", "allowSignups": true, "apiTokensEnabled": true, "allowOverridePasswordComplexity": true, "allowOverridePasswordExpiration": true, "allowOverrideEnforcePasswordHistory": true, "jwtAlgorithm": "RS256", "jwtSecret": "string", "allowNotVerifiedUsersLogin": true, "forcePermissions": true, "authStrategy": "EmailAndPassword", "defaultPasswordlessTokenExpiration": 0, "forceSameDeviceOnAuth": true, "allowTenantInvitations": true, "rotateRefreshTokens": true, "machineToMachineAuthStrategy": "ClientCredentials", "addRolesToJwt": true, "addPermissionsToJwt": true, "refreshTokensRotationLimit": 0, "addSamlAttributesToJwt": true, "allowCustomLoginTenantSwitch": true }
Create a CAPTCHA policy for all accounts (tenants).
Provide the required settings in the request body. To enable the policy, set the enabled parameter to true, and provide the siteKey and secretKey obtained from reCAPTCHA. You can also set the minimumScore parameter to a value between 0 and 1 to define the minimum score threshold.
curl -i -X POST \
https://api.frontegg.com/identity/resources/configurations/v1/captcha-policy \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"enabled": true,
"siteKey": "string",
"secretKey": "string",
"minScore": 0,
"ignoredEmails": [
"string"
]
}'{ "id": "string", "siteKey": "string", "secretKey": "string", "enabled": true, "minScore": 0, "ignoredEmails": [ "string" ], "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" }