Client Credential Flow

[faheem.riaz.kn]

I need help integrating client credential flow for a third-party api.

[tyf]

Hey there @faheem.riaz.kn welcome to the community!

Do you mind elaborating a bit on your use case and desired outcome here? Is your use case similar to the following?

How to implement 3rd-party API Authentication

What is the process for authenticating a 3rd-party Oauth 2.0 Authorization Code API? In my case, I am needing to authenticate my application’s users to access the Freshbooks API in my back end. Can this be done via a single Auth0 sign-on? When attempting to use the following link as a guide, as suspected the API returns an error, as the 3rd party API’s credentials are not contained with the Auth0 bearer token. My reference: Call Your API Using the Authorization Code Flow

The more information you can share the better!

[faheem.riaz.kn]

@tyf This is the api I want to access and They said you need to implement the Client Credential flow Guru Fitness API

I have created the App that is working and I am able to generate the token but that token does not work with the Guru API. To access this api I need to implement client credential flow as mentioned in the docs. Hope this helps
Thanks

[tyf]

Hey @faheem.riaz.kn thanks for clarifying!

@faheem.riaz.kn

I have created the App that is working and I am able to generate the token but that token does not work with the Guru API. To access this api I need to implement client credential flow as mentioned in the docs.

I believe you need to perform the client credentials flow against Guru Fitness - The access token you’re receiving currently is from an Auth0 authorization server as opposed to Guru. As far as I’m aware this is only possible using a custom social connection and retrieving an Identity Provider Access Token through a user dependent flow (not client credentials/m2m).

[faheem.riaz.kn]

@tyf I have created a custom social connection but i am getting 404,
This is the url generated when I click on test connection URL

[tyf]

It looks like your authorization and token urls are missing the 2nd / in https:// could be an issue - Just to be clear, you won’t be able to use the client credential flow with a social connection. The CC exchange will need to be carried out against the 3rd party API directly as outlined in the docs you originally referenced.