Resolving "No Token Found" in OAuth 2.0 Connections

Issue:

The connection test fails with "No token found in response" despite a successful call to the authentication server.

Resolution:

Update the Token Key field in the connection settings to match the specific key name returned by your identity provider (e.g., changing "token" to "access_token").

When configuring an OAuth 2.0 connection, ItemPath must know exactly which field in the server's JSON response contains the authorization string. If the Token Key field is misconfigured, ItemPath cannot "see" the token, even if the login was technically successful.

Provider-Specific Keys

Different identity providers user different names for their tokens. While some use a generic label, most major providers follow the standard OAuth 2.0 naming convention.

Provider	Common Token Key
Microsoft Azure	`access_token`
Generic / Custom	`token` or `bearer_token`

Updating the Token Key

Navigate to ItemPath Settings --> Connections.
Select the connection that is experiencing the "No token found in response" error.
Scroll down to the Token Settings section.
Update the Token Key to the correct value for your provider (ex: access_token).
Save and Test Connection to verify the fix.

You can verify the exact key name by checking your identity provider's API documentation or inspecting the raw JSON response from their token endpoint.