Okta IDX - Golang

Introduction

❕ The use of this SDK requires usage of the Okta Identity Engine. This functionality is in general availability but is being gradually rolled out to customers. If you want to request to gain access to the Okta Identity Engine, please reach out to your account manager. If you do not have an account manager, please reach out to [email protected] for more information.

This library is built for projects in Golang to communicate with Okta as an OAuth 2.0 + OpenID Connect provider. It works with Okta's Identity Engine to authenticate and register users.

To see this library working in a sample, check out our Golang Sample Applications.

Release status

This library uses semantic versioning and follows Okta's Library Version Policy.

Version	Status
0.x	Beta

The latest release can always be found on the releases page.

Need help?

If you run into problems using the SDK, you can

• Ask questions on the Okta Developer Forums
• Post issues on GitHub (for code errors)

Getting started

Prerequisites

You will need:

• An Okta account, called an organization. (Sign up for a free developer organization if you need one)
• Access to the Okta Identity Engine feature. Currently, an early access feature. Contact [email protected] for more information.

Install current release

To install the Okta IDX SDK in your project:

• Create a module file by running go mod init
  • You can skip this step if you already use go mod
• Run go get github.com/okta/okta-idx-golang. This will add the SDK to your go.mod file.
• Import the package in your project with import "github.com/okta/okta-idx-golang"

Usage Guide

For an understanding on how to use this library, please reference our direct auth sample repo

Configuration Reference

This library looks for the configuration in the following sources:

1. An okta.yaml file in a .okta folder in the current user's home directory (~/.okta/okta.yaml or %userprofile%.okta\okta.yaml)
2. An okta.yaml file in a .okta folder in the application or project's root directory
3. Environment variables
4. Configuration explicitly passed to the constructor (see the example in Getting started)

Higher numbers win. In other words, configuration passed via the constructor will override configuration found in environment variables, which will override configuration in okta.yaml (if any), and so on.

Config Properties

Yaml Path	Environment Key	Description
okta.idx.issuer	OKTA_IDX_ISSUER	The issuer of the authorization server you want to use for authentication.
okta.idx.clientId	OKTA_IDX_CLIENTID	The client ID of the Okta Application.
okta.idx.clientSecret	OKTA_IDX_CLIENTSECRET	The client secret of the Okta Application. Required with confidential clients
okta.idx.scopes	OKTA_IDX_SCOPES	The scopes requested for the access token.
okta.idx.redirectUri	OKTA_IDX_REDIRECTURI	For most cases, this will not be used, but is still required to supply. You can put any configured redirectUri here.

Yaml Configuration

The configuration could be expressed in our okta.yaml configuration for SDK as follows:

okta:
  idx:
    issuer: { issuerUrl }
    clientId: { clientId }
    clientSecret: { clientSecret }
    scopes:
      - { scope1 }
      - { scope2 }
    redirectUri: { configuredRedirectUri }

Environment Configuration

The configuration could alsp be expressed via environment variables for SDK as follows:

OKTA_IDX_ISSUER
OKTA_IDX_CLIENTID
OKTA_IDX_CLIENTSECRET
OKTA_IDX_SCOPES
OKTA_IDX_REDIRECTURI