Views:

Applies to Product - FnO Platform


What’s happening?
The customer is experiencing an issue where a bearer token request to an OData endpoint using Postman is prompting for sign-in instead of returning the expected access token.
 

Reason:

  • The authentication configuration of the OData endpoint may not be properly set up to accept bearer tokens.
  • The application permissions may not be correctly assigned, leading to authentication failures.
  • The token being used might have expired, necessitating a request for a new token.

 

Resolution:

  • Check Authentication Configuration: Ensure that the OData endpoint is correctly configured to accept bearer tokens. Verify the endpoint URL and the authentication settings.
  • Verify Permissions: Confirm that the application has the necessary permissions assigned. Check the permissions in the Azure portal to ensure that the app has the required delegated permissions.
  • Token Expiry: Determine if the token being used has expired. If it has, request a new token. Monitor the behavior of the integrations using OData and capture any error messages or codes displayed when authentication fails.