Connector Environment - Additional Options for Authentications

Product Suggestions
,
1

I have been working to complete and integration between Kronos and Tulip. I have been attempting to use Tulip connectors to pull the information from Kronos.

During the setup, I was able to get an initial connection when saving the connector environment, but as soon as the originating token expired, the connection failed to refresh and re-establish.

While reviewing with the Tulip support team it was realized we need to be able to alter the way that the token is refreshed and add additional information to the body.

The specific needed for the Refresh are as follows:

Refresh a token

To use a refresh token to generate a new access token and refresh token based on the credentials of the user who generated the initial refresh token, POST a call to the following authentication URI:

https://HOSTNAME/api/authentication/access_token

Include the following HTTP headers:

  • Content-Type : application/x-www-form-urlencoded

Include the following in the request body:

  • refresh_token : REFRESHTOKEN

  • client_id : CLIENT ID

  • client_secret : CLIENT PASSWORD

  • grant_type : refresh_token

  • auth_chain : OAuthLdapService

Since Tulip does not support the custom parameters like auth_chain. We are unable to maintain connections through connectors.

Expansion of the connector functions would be greatly appreciated to support further development.