Integration pages for connecting Backstage to source control platforms for catalog discovery and to identity directories for organization data, based on the Backstage integrations documentation.
Connecting Backstage to GitHub or GitHub Enterprise: GitHub App versus token credentials, repository discovery for catalog files, importing members and teams as users and groups, and webhook-driven updates instead of polling.
Discovering catalog entities across self-managed GitLab or gitlab.com, filtering groups, branches and forks, ingesting GitLab users and groups, and reacting to push webhooks.
Reading catalog files and running discovery against Azure DevOps Services or Azure DevOps Server: PAT, service principal and managed identity options, multi-organization credentials and the on-premises authentication limits.
Populating the Backstage catalog with users and groups from Entra ID through Microsoft Graph: required application permissions, user and group filters, photo loading, and incremental ingestion for large tenants. Separate from sign-in configuration.
Importing users and groups from Active Directory, OpenLDAP or FreeIPA into Backstage with the LDAP entity provider: bind accounts, attribute mapping, vendor differences, schedules and custom transformers.
Using Keycloak as the source of users and groups in the Backstage catalog alongside Keycloak sign-in, so ownership in the catalog matches the identity provider.
Connecting Backstage to Bitbucket Cloud or self-hosted Bitbucket Server (Data Center): separate integration and discovery modules for each, credentials, discovering catalog files across projects and repositories, and the matching scaffolder publish modules.
Using a self-hosted Gitea server as a Backstage source: the Gitea integration, catalog discovery through the Gitea catalog module, and creating new repositories in Gitea from Software Templates.
Reading catalog files from Gerrit code review servers, discovering projects with the Gerrit catalog module and publishing new projects from templates, for organizations that standardized on Gerrit.
Populating Backstage users and groups from Okta so catalog ownership matches the identity provider, kept separate from Okta sign-in, and how the two fit together through sign-in resolvers.
Using the AWS S3 integration to read catalog-info files stored in S3 buckets, for teams that generate catalog descriptors from pipelines or inventories rather than keeping them in repositories.
Bringing servers managed by Puppet into the catalog as Resource entities with the PuppetDB catalog module, so services can declare dependencies on the hosts they run on.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.