Hi ​@RonLevy,

First, have you gotten this working outside of Nintex, like Postman, for instance?

The only thing that sticks out for me is that the scope parameter has a colon : instead of an equals = sign to specify the value.

Hi ​@SimonMuntz 

I get the same error when using = instead of : for scope.

But I get a token if I try it with postman:

{
    "token_type": "Bearer",
    "expires_in": "3599",
    "ext_expires_in": "3599",
    "expires_on": "1741274207",
    "not_before": "1741270307",
    "resource": "00000002-0000-0000-c000-000000000000",
    "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIs...
}

And in Postman, i am using this endpoint: oauth2/token whereas I use oauth2/v2.0/token in the nintex-Workflow. Even if I change the endpoint in Nintex to oauth2/token, I get the same error.

In Postman, changing the endpoint to oauth2/v2.0/token, I get a token.

I see success in our azure login protocolls for my Postman-request, but I don’t see any log when I try to get a Token within my Nintex-Workflow

So, there might be a policy in place? (I don’t see any in my Postman-request)

Or a Nintex-Bug?
Should I open a Case?

Hi ​@RonLevy,

Check that the “Request content” field has no white space around the input as this can cause problems.

Hi ​@SimonMuntz,

has no whitespace.

I opened a Case which has been routed to development. I will let you know...

Hi ​@SimonMuntz,

the issue has been solved with the help of the Nintex-Development-Team. We have to add & between the parameters.

grant_type=client_credentials&client_id=...&client_secret=...&scope=https://tenant.sharepoint.com/.default

It is now working. Thanks for looking into it. - Have a nice day, Ronny