Last updated: 2022-12-01

Source: https://support.freshservice.com/support/solutions/articles/50000003816-centralized-credential-store

As organizations continue to grow, managing access credentials by the IT teams to authenticate requests to their third-party tools has become a productivity killer. IT teams must constantly check for the token changes and update them manually across all the workflows, which is time-consuming.

With the Centralized Credential Store,

  • Manage and reference your credentials easily while triggering webhooks or invoking web requests nodes.
  • Update your changes in the credentials store and have them reflected across all the workflows.
  • Perform any third-party calls irrespective of the authentication mechanism like OAuth 2.0, API key, and much more.

    • Creating a new Credential

    1\. Navigate to Admin → Automation & Productivity → Credentials

    2\. Click on New Credential .

    3\. Enter a Name and select the respective AuthenticationType for your Credential.

    Authentication TypeInputsDescription
    Basic AuthUsername: Email address<br>Password: PasswordUse Basic Auth type when your request involves sending a verified username and password.<br>Note: Freshservice API key authentication can be achieved by using basic auth with the following values.<br>Username: <API key><br>Password: x
    API keyKey: Authorization key specific to 3rd party<br>Value: API keyUse API key type to perform actions on applications that require an API key to authorize.
    No Auth-Use No Auth type when your request does not require authorization.
    OAuth 2.0Grant Type: The options depend on the API service provider requirements<br>1. Authorization code: The authorization code grant type requires the user to authenticate with the provider.<br> <br>2.  Client credentials: Client credentials grant type is typically not used to access user data but for data associated with the client application.<br> <br>Authorization URL: The endpoint for the API provider authorization server to retrieve the auth code.<br>Access Token URL: The provider's authentication server to exchange an authorization code for an access token.<br>Client ID: The ID for your client application registered with the API provider.<br>Client Secret: The client secret given to you by the API provider.<br>Scope: The scope of access you are requesting, which may include multiple space-separated values.<br>Client Authentication: A dropdown—send a Basic Auth request in the header or client credentials in the request body.Use OAuth type when you need to provide client applications with secure delegated access.<br>OAuth 2.0, you first retrieve an access token for the API, then use that token to authenticate future requests.<br>For apps that require redirect URL, use the below format https://<yourdomain.freshservice.com><br>/api/\_/credentials/oauth\_callback

    4\. Update the required details for each type and click on Save.

    5\. You can now reference your credentials from workflows while triggering webhooks or invoking web request nodes.