Okta: Managing Access to Groups

In this tutorial, you'll learn how to configure Grant Kits to automate access requests to an Okta User Group by attaching Okta User Group Memberships. This use case models Role-Based Access Control (RBAC) using core Okta components.

We will be using the Okta Starter Kit as a base and replace configuration stubs for our use case.

Before you start

1. Make sure you have:

   • An Abbey account

   • An Abbey API Token

   • An Okta account

2. Make sure you setup:

   1. An Okta Starter Kit by following Get a Starter Kit

   2. A Connection to a repo by following Connect a Repo

Step 1: Set Up Okta

In Okta, create a group named Has nice things

Step 2: Configure Your Grant Kit

Configure Output

Grant Kits rely on your GitHub account and repository name to output access changes, which we'll set through Terraform local variables. Update the locals block in main.tf with your account_name and repo_name

main.tf

 locals {
  account_name = "" #CHANGEME
  repo_name = "" #CHANGEME
  ...
}

Configure Reviewers

Workflow defines who should approve an access request.

Let's update the reviewers block by adding yourself as the reviewer by switching [e-mail] with the email address you use to sign into Abbey.

main.tf

 resource "abbey_grant_kit" "..." {
   ...
   workflow = {
     steps = [
       {
         reviewers = {
-          one_of = ["[e-mail]"] # CHANGEME
+          one_of = ["[e-mail]"]

Step 3: Link Okta with Abbey

Now you'll need to link Okta with Abbey.

curl -X POST \
  -H "Authorization: Bearer $ABBEY_API_TOKEN" \
  -H 'Content-Type: application/json' \
  https://api.abbey.io/v1/users/<user_id>/apps \
  -d '{"type": "okta", "data": {"user_id": "<your Okta User ID>"}}'

Step 4: Configure your Okta Settings

Replace the following settings in variables.tf

variables.tf

variable "okta_org_name" {
  type = string
  sensitive = true
- default = "dev-12345"
+ default = "dev-12345" # Use your own Okta org
}

variable "okta_base_url" {
  type = string
  sensitive = true
- default = "oktapreview.com" # CHANGEME
+ default = "okta.com" # Use the okta base where you created your API Token
}

Step 5: Deploy Your Starter Kit

First, add your GitHub-related secrets to your repo:

• OKTA_API_TOKEN

• ABBEY_TOKEN

You can find the OKTA_API_TOKEN in your Okta account. ABBEY_TOKEN is your API token

What should it look like?

To deploy your Starter Kit, follow instructions from Deploy Your Grant Kit.

Step 6: Automate Access Management

🎉 Congratulations! Abbey is now managing permissions to your Resource for you. 🎉

You can now start requesting and approving access by following the Request Access and Approve or Deny Access Requests guides.

Abbey strives to help you automate and secure access management without being intrusive.

To that end, this Pull Request contains native Terraform HCL code using normal open source Terraform Provider libraries. It represents the permissions change. In this case, it's just a simple creation of a new Terraform Resource.

Step 7: Check approved requests in Okta

Go to the okta UI and confirm that the resource you created has appeared

Next Steps

To learn more about what Resources you can configure, try one of our Step-by-Step Tutorials.

For more information on how Abbey works, visit the Key Concepts or Grant Kits page.