DevRev login process changes SSO Okta
ART-15716_KNOWLEDGE_NODE-25
not working, try resending the code or using a different phone number.\n\nIf the problem continues, escalate with the user\xe2\x80\x99s phone number, timestamp, and any error messages for backend review.\n\nOkta Integration and Forcing SSO\n\nYes, DevRev integrates with Okta for Single Sign-On (SSO). You can enforce SSO for your organization, ensuring all users authenticate via Okta. DevRev also supports SCIM for automated user provisioning and deprovisioning 12.\n\nTo set this up:\n\nGo to
Support queries related playbook
ART-15716_KNOWLEDGE_NODE-26
your DevRev admin settings.\n\nFollow the SSO setup wizard for Okta.\n\nEnable the \xe2\x80\x9cForce SSO\xe2\x80\x9d option to require all users to log in via Okta.\n\nIf you need step-by-step setup instructions or want to troubleshoot SSO enforcement, let me know!4. Input DevSlug for creating DevOrg already exists\n\nThis error means the chosen DevSlug (the unique identifier for your DevOrg) is already in use:\n\nTry a different DevSlug\xe2\x80\x94make it unique to your organization.\n\nIf you
Support queries related playbook
ART-1966_KNOWLEDGE_NODE-37
{}\n```\n```\n\n### Step 3: Test and verify the setup\n\nFollow these steps to ensure your SSO integration is working correctly:\n\n1. **Check the login page:**\n\n   * Go to: https://app.devrev.ai/<DEV\\_ORG\\_SLUG>\n   * You should see a new SSO login option with your identity provider\'s name\n2. **Test user authentication:**\n\n   * Use a test user account that\'s assigned to the DevRev application in your identity provider\n   * Click the SSO login option and complete the authentication
External identity provider setup | Computer by DevRev | DevRev
ART-1966_KNOWLEDGE_NODE-42
process from your identity provider\'s portal. The latter is not supported on DevRev.\n\nA workaround for supporting IDP-initiated SSO is to bookmark your DevRev workspace URL (that is https://app.devrev.ai/<DEV\\_ORG\\_SLUG>) in your IDP. With only SSO Auth connection enabled, the experience would be as seamless as SP-initiated SSO.\n\n### Parameter reference\n\n* <your PAT>: Your Personal Access Token with admin permissions\n* <dev\\_oid>: Your DevRev organization ID (from the initial API
External identity provider setup | Computer by DevRev | DevRev
ART-1966_KNOWLEDGE_NODE-41
}\'\n```\n\nShow more\n```\n\nImportant considerations: When disabling other authentication methods:\n\n* **Test SSO first**: Ensure SSO is working correctly before disabling alternatives.\n* **Admin access**: Make sure at least one admin can access the system via SSO.\n\nIDP initiated SSO (Optional)\n----------------------------\n\nDevRev supports SP-initiated SSO, which means users always start the authentication process from DevRev. IDP initiated SSO means users start the authentication
External identity provider setup | Computer by DevRev | DevRev
ART-4052_KNOWLEDGE_NODE-1
authentication connections, refer to [External identity provider setup](https://docs.devrev.ai/product/sso-saml).\n\nWas this page helpful?YesNo\n\n[Security tokensUp Next](/public/api-reference/auth-tokens/security-tokens)\n\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\n\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\n\nProduct\n\n  *
Identity provider — DevRev | Docs
ART-1966_KNOWLEDGE_NODE-39
authentication methods to enforce SSO-only login. This is commonly done to ensure all users authenticate through your organization\'s identity provider.\n\n**Common scenario**: If users were previously logging in with Google OAuth and you\'ve now enabled SSO, you can disable Google authentication to force all users to use SSO.\n\nFirst, get the Google OAuth connection ID:\n\n```\n```\n1 curl --location --request GET \'https://api.devrev.ai/dev-orgs.auth-connections.list\' \\\n\n\n\n2 --header
External identity provider setup | Computer by DevRev | DevRev
ART-3194_KNOWLEDGE_NODE-1
[`/accounts.list`](/public/api-reference/accounts/list-post)\n  * [`/accounts.update`](/public/api-reference/accounts/update)\n\n### Auth Connections\n\nSeveral changes to auth connection endpoints:\n\n  * Added support for `okta` as a new auth connection type\n  * Relaxed requirements for existing auth connection types (Azure AD, Google Apps, OIDC, SAML)\n  * Updated required fields for SAML connections\n\nAffected endpoints:\n\n  *
API Changelog — DevRev | Docs
ART-15499_KNOWLEDGE_NODE-1
[`/accounts.create`](/public/api-reference/accounts/create)\n* [`/accounts.export`](/public/api-reference/accounts/export-post)\n* [`/accounts.get`](/public/api-reference/accounts/get-post)\n* [`/accounts.list`](/public/api-reference/accounts/list-post)\n* [`/accounts.update`](/public/api-reference/accounts/update)\n\n### Auth Connections\n\nSeveral changes to auth connection endpoints:\n\n* Added support for `okta` as a new auth connection type\n* Relaxed requirements for existing auth
December 2, 2024 | DevRev | Docs
ART-15374_KNOWLEDGE_NODE-1
https://api.devrev.ai/dev-orgs.auth-connections.toggle \\ |\n| > | -H "Authorization: Bearer <token>" \\ |\n| > | -H "Content-Type: application/json" \\ |\n| > | -d \'{ |\n| > | "id": "string" |\n| > | }\' |\n```\n\n[Try it](/api-reference/auth-connections/dev-org-auth-connections-toggle?explorer=true)\n\n200Successful\n\n```\n|  |  |\n| --- | --- |\n| 1 | {} |\n```\n\nEnable or disable an authentication connection for a Dev organization.\nAtleast one authentication connection must be enabled
Toggle Dev Orgs Auth Connections | DevRev | Docs
ART-4060_KNOWLEDGE_NODE-1
__\n\n[Pricing](https://devrev.ai/pricing)\n\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\n\n[API Reference](/public/api-reference/getting-started)[Auth Connections](/public/api-reference/auth-connections/dev-org-auth-connections-create)\n\n# Toggle Dev Orgs Auth Connections\n\nPOST\n\nhttps://api.devrev.ai/dev-orgs.auth-connections.toggle\n\nTry it\n\nEnable or disable an authentication connection for a Dev organization. Atleast one authentication
Toggle Dev Orgs Auth Connections — DevRev | Docs
ART-1780_KNOWLEDGE_NODE-112
api.devrev.ai / dev-orgs.auth-connections.toggle\nEnable or disable an authentication connection for a Dev organization. Currently, only 1 authentication connection can be enabled at a time. When a new authentication connection is enabled, the connection which is currently enabled for the Dev organization is automatically disabled.\nRequest.\n\nThis endpoint expects an object.\nid string Required\nID of the authentication connection to be toggled.\ntoggle "disable" or "enable" Optional\nAllowed
Get Post — DevRev | Docs
ART-1785_KNOWLEDGE_NODE-111
api.devrev.ai / dev-orgs.auth-connections.toggle\nEnable or disable an authentication connection for a Dev organization. Currently, only 1 authentication connection can be enabled at a time. When a new authentication connection is enabled, the connection which is currently enabled for the Dev organization is automatically disabled.\nRequest.\n\nThis endpoint expects an object.\nid string Required\nID of the authentication connection to be toggled.\ntoggle "disable" or "enable" Optional\nAllowed
Create — DevRev | Docs
ART-1301_KNOWLEDGE_NODE-117
api.devrev.ai / dev-orgs.auth-connections.toggle\nEnable or disable an authentication connection for a Dev organization. Currently, only 1 authentication connection can be enabled at a time. When a new authentication connection is enabled, the connection which is currently enabled for the Dev organization is automatically disabled.\nRequest.\n\nThis endpoint expects an object.\nid string Required\nID of the authentication connection to be toggled.\ntoggle "disable" or "enable" Optional\nAllowed
Delete — DevRev | Docs