# Okta: Managing Access to Groups

In this tutorial, you'll learn how to configure [#grant-kits](https://docs.abbey.io/how-abbey-works/concepts#grant-kits "mention") to automate access requests to an Okta User Group by attaching [Okta User Group Memberships](https://registry.terraform.io/providers/okta/okta/latest/docs/resources/user_group_memberships). This use case models Role-Based Access Control (RBAC) using core Okta components.

We will be using the [Okta Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-okta) as a base and replace configuration stubs for our use case.

## Before you start

1. **Make sure you have:**
   * An [Abbey account](https://app.abbey.so/sign-up)
   * An [Abbey API Token](https://docs.abbey.io/admin/managing-api-tokens#creating-new-api-tokens)
   * An Okta account
2. **Make sure you setup:**
   1. An [Okta Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-okta) by following [get-a-starter-kit](https://docs.abbey.io/build-a-grant-kit/get-a-starter-kit "mention")
   2. A Connection to a repo by following [connect-a-repo](https://docs.abbey.io/build-a-grant-kit/connect-a-repo "mention")

## Step 1: Set Up Okta

In Okta, create a group named `Has nice things`

<figure><img src="https://1502779850-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FudoTqG501gLo2MLzBG55%2Fuploads%2FxL49ljDcQ1UeMTnlhZ4s%2Fimage.png?alt=media&#x26;token=198f8723-df17-4561-ba66-03f80bd00d36" alt=""><figcaption></figcaption></figure>

## 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`

{% code title="main.tf" %}

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

{% endcode %}

### Configure Reviewers

Workflow defines who should approve an access request.&#x20;

Let's update the `reviewers` block by adding yourself as the reviewer by switching `replace-me@example.com` with the email address you use to sign into Abbey.&#x20;

{% code title="main.tf" %}

```diff
 resource "abbey_grant_kit" "..." {
   ...
   workflow = {
     steps = [
       {
         reviewers = {
-          one_of = ["replace-me@example.com"] # CHANGEME
+          one_of = ["alice@example.com"]
```

{% endcode %}

## Step 3: Link Okta with Abbey

Now you'll need to link [Okta with Abbey](https://developers.abbey.io/#operation/createAppData).&#x20;

{% code title="" %}

```diff
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>"}}'
```

{% endcode %}

## Step 4: Configure your Okta Settings

Replace the following settings in `variables.tf`

<pre class="language-diff" data-title="variables.tf" data-line-numbers><code class="lang-diff">variable "okta_org_name" {
  type = string
  sensitive = true
<strong>- default = "dev-12345"
</strong>+ 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
}
</code></pre>

## 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

<details>

<summary>What should it look like?</summary>

<img src="https://1502779850-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FudoTqG501gLo2MLzBG55%2Fuploads%2FUH06xEJcSTnYbOrMiK9D%2Fokta-config.png?alt=media&#x26;token=c2a72d99-a215-4595-a771-57321a65f9b5" alt="" data-size="original">

</details>

To deploy your Starter Kit, follow instructions from [deploying-your-grant-kit](https://docs.abbey.io/build-a-grant-kit/deploying-your-grant-kit "mention").

## Step 6: Automate Access Management

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

You can now start requesting and approving access by following the [requesting-access](https://docs.abbey.io/build-a-grant-kit/requesting-access "mention") and [approving-or-denying-access-requests](https://docs.abbey.io/build-a-grant-kit/approving-or-denying-access-requests "mention") guides.

{% hint style="success" %}
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.
{% endhint %}

## Step 7: Check approved requests in Okta

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

<figure><img src="https://1502779850-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FudoTqG501gLo2MLzBG55%2Fuploads%2Fy5Vj0RWFPv8GtZ1UU5D3%2Fimage.png?alt=media&#x26;token=0ff5651e-a714-40de-9bea-8a7ce4ceede8" alt=""><figcaption></figcaption></figure>

## Next Steps

To learn more about what [resources](https://docs.abbey.io/resources "mention") you can configure, try one of our [](https://docs.abbey.io/getting-started/tutorials "mention").&#x20;

For more information on how Abbey works, visit the [concepts](https://docs.abbey.io/how-abbey-works/concepts "mention") or [grant-kits](https://docs.abbey.io/reference/grant-kits "mention") page.
