Enable self-managed OIDC auth with Okta in Dev Portal

This is a Konnect tutorial and requires a Konnect personal access token.

1. Create a new personal access token by opening the Konnect PAT page and selecting Generate Token.

2. Export your token to an environment variable:

    export KONNECT_TOKEN='YOUR_KONNECT_PAT'
   

3. Run the quickstart script to automatically provision a Control Plane and Data Plane, and configure your environment:

    curl -Ls https://get.konghq.com/quickstart | bash -s -- -k $KONNECT_TOKEN --deck-output
   

   This sets up a Konnect Control Plane named quickstart, provisions a local Data Plane, and prints out the following environment variable exports:

    export DECK_KONNECT_TOKEN=$KONNECT_TOKEN
    export DECK_KONNECT_CONTROL_PLANE_NAME=quickstart
    export KONNECT_CONTROL_PLANE_URL=https://us.api.konghq.com
    export KONNECT_PROXY_URL='http://localhost:8000'
   

   Copy and paste these into your terminal to configure your session.

This tutorial requires Kong Gateway Enterprise. If you don’t have Kong Gateway set up yet, you can use the quickstart script with an enterprise license to get an instance of Kong Gateway running almost instantly.

1. Export your license to an environment variable:

    export KONG_LICENSE_DATA='LICENSE-CONTENTS-GO-HERE'
   

2. Run the quickstart script:

   curl -Ls https://get.konghq.com/quickstart | bash -s -- -e KONG_LICENSE_DATA 
   

   Once Kong Gateway is ready, you will see the following message:

    Kong Gateway Ready
   

decK is a CLI tool for managing Kong Gateway declaratively with state files. To complete this tutorial you will first need to install decK.

For this tutorial, you’ll need Kong Gateway entities, like Gateway Services and Routes, pre-configured. These entities are essential for Kong Gateway to function but installing them isn’t the focus of this guide. Follow these steps to pre-configure them:

1. Run the following command:

   echo '
   _format_version: "3.0"
   services:
     - name: example-service
       url: http://httpbin.konghq.com/anything
   routes:
     - name: example-route
       paths:
       - "/anything"
       service:
         name: example-service
   ' | deck gateway apply -
   

To learn more about entities, you can read our entities documentation.

For this tutorial, you’ll need a Dev Portal and some Dev Portal settings pre-configured. These settings are essential for Dev Portal to function but configuring them isn’t the focus of this guide. If you don’t have these settings already configured, follow these steps to pre-configure them:

1. Create a Dev Portal:

    curl -X POST "$KONNECT_CONTROL_PLANE_URL/v3/portals" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN" \
        --json '{
          "name": "MyDevPortal",
          "authentication_enabled": true,
          "auto_approve_applications": true,
          "auto_approve_developers": true,
          "default_api_visibility": "public",
          "default_page_visibility": "public"
        }'
   

2. Export your Dev Portal ID and URL from the output:

   export PORTAL_ID='YOUR-DEV-PORTAL-ID'
   export PORTAL_URL='YOUR-DEV-PORTAL-DOMAIN'
   

3. Create a page in your Dev Portal so published APIs will display:

    curl -X POST "$KONNECT_CONTROL_PLANE_URL/v3/portals/$PORTAL_ID/pages" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN" \
        --json '{
          "title": "My Page",
          "slug": "/",
          "description": "A custom page about developer portals",
          "visibility": "public",
          "status": "published",
          "content": "# Welcome to My Dev Portal\nExplore the available APIs below:\n::apis-list\n---\npersist-page-number: true\ncta-text: \"View APIs\"\n---\n"
        }'
   

Register a test developer account with your Dev Portal by navigating to your Dev Portal and clicking Sign up:

open https://$PORTAL_URL/

For the purpose of this tutorial, we’ve set our Dev Portal to automatically approve developer registrations.

1. Create an API using the /v3/apis endpoint:

    curl -X POST "$KONNECT_CONTROL_PLANE_URL/v3/apis" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN" \
        --json '{
          "name": "MyAPI",
          "attributes": {
            "env": [
              "development"
            ],
            "domains": [
              "web",
              "mobile"
            ]
          }
        }'
   

   Export the ID of your API from the response:

   export API_ID='YOUR-API-ID'
   

2. First, send a request to the /v2/control-planes endpoint to get the ID of the quickstart Control Plane:

    curl -X GET "$KONNECT_CONTROL_PLANE_URL/v2/control-planes?filter%5Bname%5D%5Bcontains%5D=quickstart" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN"
   

   Export your Control Plane ID:

   export CONTROL_PLANE_ID='YOUR-CONTROL-PLANE-ID'
   

3. Next, list Services by using the /v2/control-planes/{controlPlaneId}/core-entities/services endpoint:

    curl -X GET "$KONNECT_CONTROL_PLANE_URL/v2/control-planes/$CONTROL_PLANE_ID/core-entities/services" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN"
   

   Export the ID of the example-service:

   export SERVICE_ID='YOUR-GATEWAY-SERVICE-ID'
   

4. Associate the API with a Service using the /v3/apis/{apiId}/implementations endpoint:

    curl -X POST "$KONNECT_CONTROL_PLANE_URL/v3/apis/$API_ID/implementations" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN" \
        --json '{
          "service": {
            "control_plane_id": "'$CONTROL_PLANE_ID'",
            "id": "'$SERVICE_ID'"
          }
        }'
   

5. Now you can publish the API to your Dev Portal using the /v3/apis/{apiId}/publications/{portalId} endpoint:

    curl -X PUT "$KONNECT_CONTROL_PLANE_URL/v3/apis/$API_ID/publications/$PORTAL_ID" \
        -H "Accept: application/json"\
        -H "Content-Type: application/json"\
        -H "Authorization: Bearer $DECK_KONNECT_TOKEN"
   

You need an admin account for Okta.