Connect DevPortal to your providers

DevPortal 3.x connects to outside systems in three separate ways. Sign-in providers are application configuration. Organization sync and catalog discovery are installable Marketplace modules with their own configuration. Repository access for the catalog and the scaffolder is application configuration under integrations.

The three mechanisms are independent. You can use GitHub repositories with Keycloak sign-in, or Microsoft sign-in with GitLab repositories, by configuring each part on its own.

Sign-in

Guest sign-in maps every visitor to the administrator identity (user:default/admin), with no password. It is for a first look only. On the local stack it comes from the guest authentication fragment, which the stack reads from config/app-config.veecode-auth.yaml. The Helm chart turns it on in chart 1.0.3 and earlier, and off from chart 1.0.4; the install guide shows the off switch on Kubernetes. Before the portal reaches real users, stop the guest authentication fragment and configure a real provider instead.

The 3.x image includes these sign-in providers, among others:

• GitHub OAuth (GitHub sign-in).
• GitLab OAuth (GitLab sign-in).
• Microsoft Entra ID (Microsoft sign-in).
• Generic OIDC, which is how Keycloak connects (Keycloak sign-in).

There is no LDAP sign-in provider in the 3.x image. To use an LDAP directory, connect it through an OIDC provider such as Keycloak (LDAP organization sync).

Each sign-in page shows the application configuration for the local stack and for the Helm chart, with placeholder credentials that you replace with your own.

Organization sync and catalog discovery

Users and groups come from Marketplace modules that import them into the catalog on a schedule. Sign-in resolves a user only when a matching User entity already exists in the catalog, so install the sync module before you test sign-in.

• GitHub users and teams: GitHub sign-in.
• GitHub repository discovery: GitHub backend integrations.
• GitLab users and groups: GitLab sign-in.
• GitLab repository discovery: GitLab integrations.
• Keycloak users and groups: Keycloak sign-in.
• LDAP and Active Directory users and groups: LDAP organization sync.
• Microsoft Entra ID users and groups: Microsoft sign-in.

Install a module from the Marketplace Extensions page, or add its package reference to an operator plugin file. Each provider page lists the exact package reference and the configuration keys for devportal-local 3.0.3.

Repository access

The catalog and the scaffolder read repositories through the integrations configuration: integrations.github, integrations.gitlab, and integrations.azure. These settings hold the tokens or application credentials the backend uses, and they are separate from sign-in.

• GitHub access and tokens: GitHub backend integrations and GitHub tokens.
• GitLab access: GitLab integrations.
• Azure DevOps access: Microsoft and Azure DevOps.

AI tooling

MCP Actions exposes catalog, scaffolder, TechDocs, and Kubernetes tools to external AI clients over HTTP, behind a static token or per-user OAuth.