> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/workspace/sso-auth-okta.md).

# SSO Integration (Okta)

## Hackle SSO Integration Guide with Okta

This guide walks you through setting up SSO (Single Sign-On) for Hackle using Okta.

### Prerequisites

* Okta administrator account
* Hackle administrator account
* Hackle Enterprise plan subscription or higher

### 1. Configure Application in Okta

#### 1.1 Create a New Application in the Okta Admin Dashboard

1. Log in to the Okta Admin Portal
2. Navigate to Applications > Applications
3. Click the 'Create App Integration' button
4. Select 'SAML 2.0' for the Sign-in method
5. Click 'Next'

#### 1.2 SAML Configuration

Enter the following information in General Settings:

* App name: "Hackle"
* App logo: Optional. You can upload the Hackle logo.

Enter the following information in SAML Settings:

```
Single Sign On URL: https://app.hackle.io/sso/saml2/acs
Audience URI (SP Entity ID): https://app.hackle.io/sso/saml2/metadata
Name ID format: EmailAddress
Application username: Email
```

#### 1.3 Configure Attribute Mapping

Map the SAML attributes as follows:

* First Name: user.firstName
* Last Name: user.lastName
* Email: user.email
* Role: user.role (optional)

### 2. Configure SSO in Hackle

#### 2.1 Hackle Admin Configuration

1. Log in to the Hackle Dashboard
2. Navigate to Settings > Authentication
3. Click the 'Configure SSO' button

#### 2.2 Configure Okta Metadata

Copy the following information from Okta and enter it in Hackle:

* Identity Provider Single Sign-On URL
* Identity Provider Issuer
* X.509 Certificate

### 3. Test the Integration

#### 3.1 Configure Test User

1. Create a test user in Okta or select an existing user
2. Assign the Hackle application to that user

#### 3.2 Test SSO Login

1. Open a private browser window
2. Navigate to the Hackle SSO login URL
3. Attempt to log in using Okta credentials
4. Verify that you are successfully redirected to Hackle

### 4. Troubleshooting

Common issues and solutions:

* SAML Response error
  * Verify that the attribute mapping in Okta is correct
  * Verify that the certificate is valid
* Login failure
  * Verify that the user has been assigned the appropriate permissions
  * Verify that the Hackle account is activated

### 5. Security Settings (Optional)

Recommended settings for additional security:

* Configure IP allowlisting
* Set session timeout
* Enforce a strong password policy

### Support and Contact

If you encounter issues during the integration process, you can get support through the following channels:

* Hackle Technical Support: <support@hackle.io>
* Technical Documentation: docs.hackle.io


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/workspace/sso-auth-okta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.