# SCIM 2.0 with Bearer Authentication

1. Any application which supports SCIM v2.0 with bearer token is workable for application.<br>

   <figure><img src="https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/84003459811/original/PSROuSBIchNyli__tGejfJE4XLTOK7bpxg.png?1649374849" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/84003459814/original/eWZHLXTTUNIfL7I_RDyfB5qTghrAU-7sXA.png?1649374869" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/84003459840/original/uHqKKvrJ6ZMP6tV-TDINn8ssl0F0fwASlQ.png?1649374883" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/84003459860/original/xXORmTT9bkY_ZlS76tn54MxZ1VI-6mGAPw.png?1649374894" alt=""><figcaption></figcaption></figure>
2. Following are configuration which is used for SCIM with bearer.
   1. Base address - It is the endpoint of the target system which supports SCIM v2 API’s.
   2. Username - Username to authenticate SCIM API endpoint.
   3. Password - Password to authenticate SCIM API endpoint.
   4. Security Token - It is a token which is used to authenticate.
   5. Grant Type - It is grant type which is used to grant access for API’s.
   6. Client Id - client id for authentication
   7. Client Secret - client secret for authentication
   8. Authentication type - It is Fixed Bearer compulsory.
   9. Update method - Patch or Put method.
   10. Accept - Http header which accepts (application/json etc).
   11. Content Type - Http header which accepts (application/json etc).
   12. Access Token Base Address - base address for access token
   13. Access Token Node Id - node id for access token
   14. Access Token Content Type - content type for access token.


---

# Agent Instructions: 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:

```
GET https://help.cymmetri.io/lifecycle-management/application-management/provisioning-how-to/scim-2.0-with-bearer-authentication.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.