Common authentication methods for secure portal access

Select and configure the appropriate authentication mechanism to align your developer portal with enterprise security standards and external toolchain requirements.

Corporate Single Sign-On (SSO)
Select this option to use your standard organizational credentials. This method typically provides full access to internal resources and links your portal identity to your official team membership.
Federated authentication
Use services such as Keycloak or Ping Federate to unify your login across many enterprise applications. This makes sure that your permissions remain consistent as you navigate between the portal and external development tools.
OAuth providers
Select providers such as GitHub, GitLab, or Azure DevOps to link your developer identity directly to the portal. You must use this method if you need to perform actions in the Software Catalog that involve external version control systems.
Guest access

Use this restricted, read-only mode for initial platform exploration.

Important

Use Guest access for demonstration purposes only. While in this mode, you cannot register components, use Software Templates, or access restricted organizational data.