> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/sso-connect-cloud/passwordless-providers/traitware.md).

# Traitware

How to configure Keeper SSO Connect Cloud with Traitware for Passwordless login to Keeper.

### **Configure Keeper for Traitware Integration**

Visit the [Keeper Admin Console](https://keepersecurity.com/console) and login as the Keeper Administrator.\
\
<https://keepersecurity.com/console> (US / Global)\
<https://keepersecurity.eu/console> (EU-hosted customers)\
<https://keepersecurity.com.au/console> (AU-hosted customers)\
<https://govcloud.keepersecurity.us/console> (GovCloud customers)

{% hint style="success" %}
Note: Passwordless integration can only be applied to specific nodes (e.g. organizational units) within your Admin Console.
{% endhint %}

Click on the **Admin** tab and click **Add Node**.

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhZYhfRRmWDM7ByKmAJ%2F-MhZ_pPLwdMqeaig5f9S%2FAdd%20a%20Node.gif?alt=media\&token=d92b17e1-30ad-409d-ad50-18b3df84c65b)

From the **Provisioning** tab, click **Add Method**

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhZDS7bVTAXLQUHomFj%2F-MhZRD9oPwAZQEcCeoqu%2Fimage.png?alt=media\&token=46484c31-8d2e-4aab-b804-ef5ae5d15085)

Select **Single Sign-On with SSO Connect™ Cloud** and click **Next**

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhZDS7bVTAXLQUHomFj%2F-MhZRVqBIAuznR2MhHrC%2Fimage.png?alt=media\&token=edb5ad5b-e0bf-4a29-b9ed-59fa91624171)

Enter your **Configuration Name** and **Enterprise Domain**, then click **Save**. Take note of the Enterprise Domain. This will be used later for Enterprise SSO login.

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhZDS7bVTAXLQUHomFj%2F-MhZRqWfE0IbtSAeCt6Q%2Fimage.png?alt=media\&token=6aa68c3b-fa4e-48f8-b192-e73166c25cfa)

The newly-created SAML 2.0 with Cloud SSO Connect provisioning method will be visible. Select **View** from the menu.

{% hint style="success" %}
Note the **Entity ID** and **Assertion Consumer Service (ACS) Endpoint**. These values will be used when configuring TraitWare.
{% endhint %}

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhZDS7bVTAXLQUHomFj%2F-MhZWUzB3ZOu4NyLB2vE%2FView%20Cloud%20SSO%20Connect%20Provisioning%20Method.gif?alt=media\&token=020a24d9-f1ab-41af-9219-e514aa948824)

### Configure TraitWare

Log into the TraitWare Admin Console (TCC) <https://api.traitware.com/console/login>

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-Mh_6xUnwJhp7XU4VxVH%2F-Mh_DPtw-r9N1jlcyf7-%2FLogin%20to%20Traitware.gif?alt=media\&token=61d21426-7dca-47ec-9b4a-6ac3990d27dc)

#### Generate Application Key

Select the **Signing Keys** from the left menu. Click **Generate new Key Pair** button. Enter the application name for the key pair. Select desired **Lifetime in Years**, **Product Key Type** and **Product Key Size**. Click **Generate Key**.

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-Mh_6xUnwJhp7XU4VxVH%2F-Mh_FAVQROyg2Fb1tn5T%2FTraitware%20Signing%20Keys.gif?alt=media\&token=f56b749e-70cb-4a12-ab38-09f1ca750f89)

#### Create Traitware Application

1. Select **Applications** from the left menu and click **Add Application**.
2. Select **SAML 2.0**.
3. Click **Use a Template** and select **Keeper**
4. Insert your **Keeper Entity ID** and **Assertion Consumer Service (ACS) Endpoint** noted previously in the walkthrough and click **Submit**.

{% embed url="<https://vimeo.com/591345332/5fab85fd65>" %}

#### Configure SAML 2.0 Integration

1. From the Traitware Admin Console Applications tab, select **Keeper**
2. Select the **Provider Credentials** tab and click the download icon for **Traitware IdP SAML Metadata (XML)**
3. Click **Save Application**
4. Return to the Keeper Admin Console
5. Edit the **SAML 2.0 with Cloud SSO Connect™** provisioning method
6. Upload the file from step 2 to the **SAML Metadata** field

{% embed url="<https://vimeo.com/591303969/9a3ba9868f>" %}

#### Create and Enable Users to Login to Keeper Vault through Traitware

1. From the Traitware Admin Console **Users** tab, select **Create User**
2. Complete the form and click **Save Changes**
3. Click on the newly created user and select the **Applications** tab
4. Toggle **Application Access** on for **Keeper**

{% hint style="success" %}
Note: A user with the same email address must also exist within the Keeper Admin Console. For more information on creating Keeper users, see [Manual Addition of Users](/enterprise-guide/user-and-team-provisioning/manual-provisioning-through-admin-console.md) in our enterprise documentation.
{% endhint %}

{% embed url="<https://vimeo.com/591306916/4f24a60ab9>" %}

#### Enable All Traitware Users to Login to Keeper Vault through Traitware

1. From the Traitware Admin Console **Applications** tab, select **Keeper**
2. Click Enable All User Access
3. Confirm the action and click **Enable Access**

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhpJQGdOKtY9WMfeinX%2F-MhpW5iqxP9742vxvRqF%2FEnable%20All%20Users%20to%20Login%20to%20Keeper%20through%20Traitware.gif?alt=media\&token=303fba2b-fbb7-4307-8527-ea58860ce1ee)

### End User Login

Users may login either using their enterprise domain or email address.

#### **Login Using Email Address**

1. Navigate to the Keeper Vault
2. Enter your email address and click **Next**
3. From your Traitware app on your smart device, scan the QR code on your desktop browser
4. You will now be logged in to your Keeper vault

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhyUamfNA2x0zwD5QQk%2F-MhyWzXgkKyBPWQmbEkJ%2FLogin%20to%20Keeper%20with%20Traitware%20with%20Email%20Address.gif?alt=media\&token=bb8d388d-1fd6-46a0-9592-c5b1be6b480b)

**Login Using Enterprise Domain**

1. Navigate to the Keeper Vault
2. Click the **Enterprise SSO Login** dropdown and select **Enterprise Domain**
3. Enter the Enterprise Domain name you specified in the Keeper portion of this walkthrough and click **Connect**
4. From your Traitware app on your smart device, scan the QR code dispalyed on your desktop browser
5. You will now be logged in to your Keeper vault

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MhyFJ0jxYZjUfF1sNI2%2F-MhyU7qw2SyLskhv-iMP%2FLogin%20to%20Traitware%20with%20Keeper%20with%20Enterprise%20Domain.gif?alt=media\&token=8cc5d322-9e26-4047-aaa0-72d43ce1c0c9)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/sso-connect-cloud/passwordless-providers/traitware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
