> For the complete documentation index, see [llms.txt](https://docs.novacura.com/extensibility-and-integration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/extensibility-and-integration/products/studio/connectors/rest-connector/how-to-guides/authenticate/oauth2.md).
# OAUTH2
How to authenticate in different ways
## OAUTH2 - as Operation inside the Project
To learn more about Oauth2 and Authentication around REST, the Postman help section gives a good in depth look. It can be found at:
In Flow the connection can either be set up as it's own connector (External Oauth2 provider), or set it up within the Rest-project itself. This is an example with Flow set up against Salesforce with 5 input parameters (string). The response is captured under the OK response.
Note that the parameters are as FormData type
If the input body in Postman is of type x-www-form-urlencoded:
you will have to change the content typ to application/x-www-form-urlencoded
## OAuth2- using the specific Connector
If you choose to set up the authentication with the Oauth2-connector it may look like this which is an example of a connection with Microsoft Office 365
In the O365 case the token has to start with "Bearer", easily obtained like this:
---
# 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.novacura.com/extensibility-and-integration/products/studio/connectors/rest-connector/how-to-guides/authenticate/oauth2.md?ask=&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.
