Authentification Failed "Get new access token"

[LeoCdis]

Is there an existing issue for this?

• I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

Hello to all,

For more than one week , I can't create any token via postman : still the same mistake message : Authentication failed (you can see the picture).

I would like to create token to access coding for "OAuth 2.0". I have a V10.7.0 version.

I have looked on some forums that you have to enable POP-UPS. I did it, but it still doesn't work. If anyone can help me please?

Steps To Reproduce

A

Screenshots or Videos

No response

Operating System

Windows

Postman Version

10

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

[LeoCdis]

@postman-support

[abhijeetborole]

Hey @LeoCdis , could you share the error message you're seeing on the Postman Console?

Also, is this an id_token?

[LeoCdis]

Hey @abhijeetborole
thank you for your answer. Here is what I have on my postman

[LeoCdis]

@abhijeetborole
POST http://{{tokenurlinternal}}/: {
"Error": "DNSLookup: ENOTFOUND {{tokenurlinternal}}",
"Request Headers": {
"content-type": "application/x-www-form-urlencoded",
"authorization": "Basic e3tvcmNoZXN0cmF0b3JDbGllbnR9fTp7e29yY2hlc3RyYXRvclNlY3JldH19",
"user-agent": "PostmanRuntime/7.30.0",
"accept": "/",
"cache-control": "no-cache",
"postman-token": "c7567ae3-45e1-4d48-97d4-4b41ec230de5",
"host": "{{tokenurlinternal}}",
"accept-encoding": "gzip, deflate, br",
"connection": "keep-alive"
},
"Request Body": {
"grant_type": "client_credentials",
"scope": "openid"
}
}
Error: DNSLookup: ENOTFOUND {{tokenurlinternal}}

[abhijeetborole]

@LeoCdis it looks like the tokenurlinternal variable was not resolved, could you confirm if it is enabled in globals/environments/collection variables and the right environment is selected?

[LeoCdis]

@abhijeetborole I have selected a new environment, but I get another error message at this point.

[abhijeetborole]

@LeoCdis It could be that the server here expects the client credentials in body. Could you try setting Client Authentication to Send client credentials in body?

Also, are either client_id or client_secret here empty?

[LeoCdis]

@abhijeetborole I can't figure out what to do? I have to click on which button and give which information?

[LeoCdis]

and no @abhijeetborole :

[abhijeetborole]

@LeoCdis Click the dropdown next to Client Authentication -> Select Send client credentials in body

[LeoCdis]

@abhijeetborole @DannyDainton
I'm sorry for the late reply. I just tried the manipulation but it still doesn't work. My colleagues manage to create a token with the same client field as the one shown on the screenshot.

[jtowe1]

The "Send client creds in body" is what I was missing. Was that added or changed in an update?

[abhijeetborole]

Hey @LeoCdis , could you share your and your colleague's configuration? Not sure who the one above belongs to 😅

@jtowe1 We've had this option under Client Authentication for a while now 😅

The "Send client creds in body" is what I was missing. Was that added or changed in an update?