Skip to content
Kong Docs are moving soon! Our docs are migrating to a new home. You'll be automatically redirected to the new site in the future. In the meantime, view this page on the new site!
Kong Logo | Kong Docs Logo
  • Docs
    • Explore the API Specs
      View all API Specs View all API Specs View all API Specs arrow image
    • Documentation
      API Specs
      Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong AI Gateway
      Multi-LLM AI Gateway for GenAI infrastructure
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Kong Gateway Operator
      Manage your Kong deployments on Kubernetes using YAML Manifests
      Insomnia
      Collaborative API development platform
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      AI's icon
      AI
      Govern, secure, and control AI traffic with multi-LLM AI Gateway plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
  • Home icon
  • Konnect Dev Portal
  • Portals
  • Settings
  • Add Developer Teams from Identity Providers
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • Portals
    • Overview
    • Customization
      • Customization
      • Pages
      • Snippets
      • Appearance
      • Portal Editor
    • Publishing APIs
    • Settings
      • General
      • Custom Domains
      • Security
      • Team Mapping
    • Audit Logs
  • APIs
    • Overview
    • Versioning
    • Documentation
    • Link Gateway Service
  • Access and Approvals
    • Overview
    • Developer Signup
    • Configuring SSO
    • Portal Teams
  • Application Registration
    • Overview
    • Auth Strategies
      • Key Auth
      • OIDC
        • Overview
        • DCR
          • Overview
enterprise-switcher-icon Switch to OSS
On this pageOn this page
  • Prerequisites
  • Set up developer teams and group claims in your IdP
  • Map IdP developer teams in Konnect
  • Test developer team mappings

Add Developer Teams from Identity Providers

In the Konnect Dev Portal, you can map existing developer teams from a third-party identity provider (IdP) and their permissions to elements in Konnect. With teams mapped from an IdP, the developers and permissions are mapped automatically in Konnect so you don’t have to manually copy over each team of developers.

This guide explains how to map the permissions, including scopes and claims, from your group of developers in your IdP to your organization’s team in Konnect. Although this guide uses Okta, Azure Active Directory (AD), and Auth0 as examples, you can use any IdP that conforms to OIDC standards.

Prerequisites

  • A test developer account in your IdP
  • An application for Konnect configured in your IdP:
    • Okta
    • Azure AD
    • Auth0

Set up developer teams and group claims in your IdP

Okta
Azure AD
Auth0
  1. In Okta, assign people to a group, including your test developer account. Alternatively, you can use group rules to automatically add people to a group.

  2. Configure any other group settings and attributes as needed.

  3. Enable group push for Kong Gateway to push existing Okta groups and their memberships to Konnect.

  4. Add a groups claim for the org authorization server.

  1. In Azure AD, create a new group that includes your test developer account.

  2. Configure a groups claim.

  1. In Auth0, create a new team of developers that you want to map to Konnect. Make sure to add your test developer account.

  2. Configure a groups claim.

Map IdP developer teams in Konnect

  1. In dev-portal icon Dev Portal, click Settings.

  2. In the General setting tab, enable Portal RBAC.

    Enabling RBAC allows you to create teams in Konnect. You can disable RBAC after you map teams from your IdP if you don’t want to use it.

  3. From the Teams settings in the side bar, click New Team and configure the team.

  4. From the IdP team you just created, click the APIs tab and click Add Roles. This allows you to assign APIs and the role for the APIs to members of your IdP team.

  5. From Settings in the Dev Portal side bar, click the Identity tab and then click Configure OIDC provider.

  6. Configure the IdP settings using the following mappings:
    • Provider URL: The value stored in the issuer variable from your application in your IdP.
    • Client ID: The application ID from your application in your IdP.
    • Client Secret: The client secret from your application in your IdP.
    • Scopes: The scopes to be requested from your application in your IdP.
    • Claim Mappings - Name: name
    • Claim Mappings - Email: email
    • Claim Mappings - Groups: groups
  7. Click the Team Mappings tab, and then select IdP Mapping Enabled.

  8. Enter the exact name of your team from your IdP next to the name of the Konnect team you want to map it to.

Test developer team mappings

Now that you’ve configured the IdP team mappings in Konnect for the Dev Portal, you can test the team mappings by logging in to the Dev Portal with a test account that is assigned to the team in your IdP.

  1. Navigate to your Dev Portal URL and log in as a test developer that is assigned to the team in your IdP. You can find your Dev Portal URL in the Dev Portal settings in the Portal Domain tab.

  2. If the mappings are correct, you should see any APIs that you assigned to the team in Konnect.

Once a developer in your IdP team signs into the Dev Portal, they will be populated as a new developer associated with that team in Konnect. You can verify this by going to the Dev Portal teams settings in Konnect. The test developer should be listed there as a developer associated with your team.

Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • Kong
    Powering the API world

    Increase developer productivity, security, and performance at scale with the unified platform for API management, service mesh, and ingress controller.

    • Products
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • Product Updates
      • Get Started
    • Documentation
      • Kong Konnect Docs
      • Kong Gateway Docs
      • Kong Mesh Docs
      • Kong Insomnia Docs
      • Kong Konnect Plugin Hub
    • Open Source
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kong Community
    • Company
      • About Kong
      • Customers
      • Careers
      • Press
      • Events
      • Contact
  • Terms• Privacy• Trust and Compliance
© Kong Inc. 2025