Bringg supports the following authentication methods for Webhooks:
|JSON Web Token (JWT)
|This method consists of three parts: a header, a payload, and a signature. The header contains information about the type of token and the algorithm used for the signature. The payload contains the claims or information about the user or entity being authenticated. The signature is created by hashing the header and payload with a secret key to ensure the integrity of the token.
|Include Client ID, Client Secret, Auth URL, Path, Request Type, and Scope.
|Include an authorization token or API key in the header of the HTTP request.
You can configure JWT and OAuth 2.0 via the Authentication Methods page.
Configure static headers within each individual webhook - see Step 5 of the Procedure outlined in Bringg Webhooks for instructions.
To add a new Authentication Method for webhooks:
- Select your username > Settings > Platform Integrations > Authentication Methods
- Click Add Authentication Method
- In Use for, choose Webhooks
- Enter a Display name for the authentication method that you and other members of your team will recognize.
- Select the relevant type, either JWT or OAuth 2.0
- Enter the relevant details for the selected method.
- You must include a Client ID, Client secret, Authorization URL (and path to an endpoint to retrieve tokens), and the request type/
- (Optional) If you'd also like to add static headers to all webhooks using this authentication method, you can add the relevant key-value pairs in the Headers section.
- You must include a Signature key, the Issuer, the Algorithm, the Audience, and the Subject.
Updated 3 months ago