AuthId

[daveblack93]

Hi team,
I have forked the repo, cause I would like to develop a dotnet core wrapper to be used for calling authenticated endpoint (like for example Github /user).
I would like to obtain the authId value stored by the backoffice (that manage the OAuth challenge).
Is there any API that I can call (from postman for example) having the SetupID or ClientID (or something else :D) of the integration?
From the JS example seems that the only way to retrieve an authId is when you challange the authentication by this method:
github.connect().then(({ authId }) => { // The authentication was successful console.log(Auth ID is: ${authId}) }).
Thank you,
Dave.

[daveblack93]

Can I add in the api.ts and open you a PR in order to integrate an endpoint like this one below in order to retrieve the auth_id having the setup_id?

`api.get('/:integrationId/authentication/:setupId', async (req, res) => {
  const buid = String(req.params.integrationId)
  const setupId = String(req.params.setupId)
  const authentication = await store('authentications')
    .select('auth_id', 'setup_id', 'created_at', 'updated_at')
    .where({ buid: buid, setup_id: setupId })
    .first()

 res.json(authentication)
})`

[markmichon]

I'm not sure if I completely understand the use case. How would you know which authId you are requesting?

The setupId is associated with an 'application' on the service you're connecting to. Github for example. An authId is associated with an individual user (or more specifically, an instance of authentication with the API). In the example above you'd be receiving all authentications (kind of like if pizzly offered a get to /:integrationId/authentications) for that application. As far as I can tell, you wouldn't be able to then reconcile that id with the correct user in order to make the request.

You can certainly recreate the functionality of the client in dotnet, but you'd need to handle the auth approval dance between your code, the service, and pizzly-or manually set the authId. The node client is an example of this in action.

[daveblack93]

Hi Mark,
basically now I have installed Pizzly on my cluster and I will use the UI provided only for handle the auth approval dance.
When I instantiate my dotnet client I will create a new configuration (if the setupId is not provided in configuration or it doesn't exists anymore).
When I got the setupId (from the configuration or registering a new instance of the application) I would like to obtain the authId (because the approval dance) is managed by the standard UI and not from my dotnet code.
With the API that I wrote in my previous post I can obtain the authId using the setupId.