kamermans/guzzle-oauth2-subscriber

Unable to get "Client Scoped Token"

TMWagner opened this issue · 0 comments

The API I am trying to authenticate with defines this workflow:

If you haven’t already been granted access to the xxx Operations API, you should contact your sales representative and request access. Once this step has been done, you should have a username, password and refresh token for your API account. You will need this information to authenticate to the API.

Authentication Workflow
The authentication workflow comprises of two steps:

Use your refresh token to get a client-scoped access token
Use the client-scoped access token to access resources
For each step, the Authorization header must be present.

In Postman I am able to obtain a "Client-scoped access token" (see graphic)
2019-10-28_20-21-36

However, the documentation here on GitHub does not give any clue as to how to provide the provided static refresh token in the authentication process.

Is there any way to do that?

Seems everything else is working. If I take the "Client-scoped Token" generated by Postman manually add it, I'm able to make subsequent resource requests