Troubleshooting An Unusable Access Token

2024-08-09T04:00:00Z
I am using Postman for the first time today. I am working on a project to switch an existing Power BI report to an API associated with our ERP system. I am using Postman to provide connectivity-related information for my report.

We are using Infor’s Sytline for our ERP system. I am trying to establish communication with an Infor provisioned API named "Enterprise Quoting (CPQEQ). I am trying to create an access token for this API in Postman. I appear to have created one following steps found in Infor’s knowledgebase. The access token authenticates but the “Use Token” button is inactive.

I am wondering if someone might have the time to help me understand why this has occurred and what it means. I don’t expect a 1:1 tutoring session. It would be great if someone would respond with a quick answer, if possible, or point me in the right direction with online documentation. Thank you in advance for considering this request.

Can you please provide links to the API documentation. In particular the part related to authentication and details on what authentication providor is being used in the solution.

I suspect its using OAuth 2.0. This is Microsofts implementation for client credentials. The site has other page related to other grant types so you need to tell us what grant type is being used for authentication.

Most authentication providors work the same way, as OAuth 2.0 is a standard. But there are some slight variances, so its normally a case of visiting the website for the authentication providor to get a more indepth knowledge of that particalar setup.

Can you also show screenshots of what you have in Postman (redacted as appropriate) to help us understand what you are having issues with.

The authentication tab (aka authentication helper) in Postman does a lot of stuff under the hood, but to troubleshoot effectively, you need to understand the authentication being used.

The authentication helper in Postman takes a lot of the leg work out of authentication. In particular for grant types that require user/browser interaction which you can’t normally automate. For most of the other grant types, you could in create standard requests in Postman to hit the various end points in order. Harder to do, but this way it ensure you understand the actual order of authentication and becomes easier to troubleshoot when you have issues.

Hello, Mike,

Thank you for your prompt response and patience with my inexperience. :slightly_smiling_face: I am working towards providing you with the information you have asked for. Please find the link I have attached to this response for more information regarding Postman’s settings needed for Infor APIs. I will continue to provide information as it becomes available.

> Infor API Connection Information.

That documentation is telling you how to configure this, and even has instructions for Postman.

It is using the password grant type.

On a side note, password credentials for this type of “service account” connection is unusual. It would normally be client credentials.

Password is normally used when you want to authentice with multiple roles and permissions. If its a single service account controlling access, then client credentials is more appropriate.

However, you can either use the authentication helper like the documentation is guiding you through, or you can create this as a normal request like the following.

Then retreive the token in a post response script.

Something like.

response = pm.response.json();

pm.collectionVariables.set("bearerToken", response.id_token); // used in the authorisation header bearer token

You would then consume the token by setting it in the auth tab for the subsequent requests.

@michaelderekjones, Thank you for the link you sent in your last chat. I’m going to give it a go and will let you know the outcome.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.