> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/identity-and-access.md).
# Identity and Access
Trulyp supports five methods for users to sign in. **Username + Password**, **Single Sign On**, **OAuth,** **Tableau Auth** and **Power BI Auth.** Choose below which (one or multiple) versions of authentication you would like to use, and follow the instructions to set it up.
{% tabs %}
{% tab title="Username + Password" %}
This is the basic username + password authentication method. You can configure username and password in the members section. This method will force every user which uses the extension to login first.
*When also using the tableau user sync, the administrator should manually set a password for every user.*
{% endtab %}
{% tab title="Single Sign On" %}
Trulyp supports Single Sign-On through SAML. Any provider supporting SAML is supported by Trulyp. We have made some examples of the major SSO providers (Azure, Okta, Ping) which you can use to derive the configuration for your SSO Provider.
#### **What is needed for a SSO Setup**
* Create an app in your identity provider
* Assign the users and groups
* Set Reply URL's
* Set Attributes
* Add the following information from the app in your identity provider to Trulyp:
* SP Entity ID, Entity ID, Login URL, iDP Certificate
#### Step-by-step instructions
1. Make sure you have a SSO provider like Okta, Azure, Ping, Google or other.
2. Create a new app in your Identity Provider.
3. Assign users and groups to the app.
4. Generate a SP Entity ID and fill it in your app. Note that this should not contain special characters. Remember the value, you will need it in step 9.
5. Set Reply URLs. Copy the Reply URLs from the Management Console.
6. Set the Sign On URL This is **/backend/login (Also called Assertion Consumer Service URL).
7. Set the Attributes similar to the image below.
8. Your app is ready to use.
9. Copy the SP Entity ID from step 4 and paste it in SP Entity ID field. (Azure: Identifier, Okta: Audience URI)
10. Copy the IdP Entity ID from the app and paste it in IdP Entity ID field. (Azure: Microsoft Entra Identifier, Okta: Identity Provider Issuer).
11. Copy the Login URL from the app and paste it in Login URL field. (Azure: Login URL, Okta: Identity Provider Single Sign-On URL).
12. Copy certificate (X.509) from the app to IdP certificate field.
13. Click the test SAML/SSO Button.
14. If SSO is successful click on Apply Config.
15. Click on Save (Top of page).
For examples, you can click here:
{% content-ref url="/pages/PCGiAD74ejeooqCUqxjZ" %}
[OKTA Example](/trulyp/identity-and-access/sso/okta-example.md)
{% endcontent-ref %}
{% content-ref url="/pages/3siazQUa6spmKbdDAqD3" %}
[PingOne Example](/trulyp/identity-and-access/sso/pingone-example.md)
{% endcontent-ref %}
{% content-ref url="/pages/6R1UCo9CLxJDwNZkqiRw" %}
[Azure Example](/trulyp/identity-and-access/sso/azure-example.md)
{% endcontent-ref %}
{% content-ref url="/pages/wHW8mKwaUyelFzo1sk6b" %}
[Troubleshooting SSO](/trulyp/identity-and-access/sso/troubleshooting-sso.md)
{% endcontent-ref %}
{% endtab %}
{% tab title="OAuth" %}
Setting up OAuth authentication is very straightforward. For most providers, only a **client id** and **secret** is needed for the setup. At the moment of writing we support **Microsoft Entra, Google, Okta, Salesforce** and **Auth0**.
For the setup you will need to create an app registration with your provider. We have examples of the most common providers included here in the documentation. Other providers will have a different interface and maybe use different terms but the procedure is mostly the same.
{% content-ref url="/pages/v3Ms5fBRNo3QimTirsgL" %}
[Microsoft Entra](/trulyp/identity-and-access/oauth/microsoft-entra.md)
{% endcontent-ref %}
{% content-ref url="/pages/vIrXTuy3yk7UIwyfRi5k" %}
[Auth0](/trulyp/identity-and-access/oauth/auth0.md)
{% endcontent-ref %}
{% content-ref url="/pages/CgSuJNxJL2R4yWSJsbPx" %}
[Google](/trulyp/identity-and-access/oauth/google.md)
{% endcontent-ref %}
{% endtab %}
{% tab title="Tableau" %}
Using the Tableau REST API you’re able to authenticate any user with Tableau Server or Tableau Online.
If the Username and Password matches an account on Tableau Server the extension will start. This will need to be a local Tableau account, not a SSN.
To enable this method of authentication, fill in your Tableau server URL, the Tableau site, and Tableau API version and press "Apply config".
{% endtab %}
{% tab title="Power BI" %}
{% endtab %}
{% endtabs %}
---
# 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.infotopics.com/trulyp/identity-and-access.md?ask=&goal=
```
`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.
6. Set the Sign On URL This is *
8. Your app is ready to use.
9. Copy the SP Entity ID from step 4 and paste it in SP Entity ID field. (Azure: Identifier, Okta: Audience URI)
10. Copy the IdP Entity ID from the app and paste it in IdP Entity ID field. (Azure: Microsoft Entra Identifier, Okta: Identity Provider Issuer).
11. Copy the Login URL from the app and paste it in Login URL field. (Azure: Login URL, Okta: Identity Provider Single Sign-On URL).
12. Copy certificate (X.509) from the app to IdP certificate field.
13. Click the test SAML/SSO Button.
14. If SSO is successful click on Apply Config.
15. Click on Save (Top of page).
For examples, you can click here:
{% content-ref url="/pages/PCGiAD74ejeooqCUqxjZ" %}
[OKTA Example](/trulyp/identity-and-access/sso/okta-example.md)
{% endcontent-ref %}
{% content-ref url="/pages/3siazQUa6spmKbdDAqD3" %}
[PingOne Example](/trulyp/identity-and-access/sso/pingone-example.md)
{% endcontent-ref %}
{% content-ref url="/pages/6R1UCo9CLxJDwNZkqiRw" %}
[Azure Example](/trulyp/identity-and-access/sso/azure-example.md)
{% endcontent-ref %}
{% content-ref url="/pages/wHW8mKwaUyelFzo1sk6b" %}
[Troubleshooting SSO](/trulyp/identity-and-access/sso/troubleshooting-sso.md)
{% endcontent-ref %}
{% endtab %}
{% tab title="OAuth" %}
