...
When the access has been created, the recipient must receive this information along with other important information so that they can start reviewing the documentation and obtain the access token.
The token must be sent manually to the recipient for security reasons, but the remaining information that the recipient needs will be triggered for sending via email by clicking on the email icon that appears once you have added the client.
Here is the information sent to the recipient (hostname is automatically set to the correct feed URL name):Here is a suggested text that can be sent to the user:
---------------------------------------------------------------------------------------------------------
Hello and welcome as a user of the FEED API.
To get started with integration, you can read the API documentation at:
https://<hostname>/export/swagger-ui/
https://<hostname>/import/swagger-ui/
https://<hostname>/media/swagger-ui/
To use the API, you need to must use Oauth OAuth 2.0 to obtain an access token.
Client ID: Enter feed client ID
Client secret: Enter feed client key
Grant type:
Client Credentials with Basic Auth Header
Token server:
For more information see https://<hostname>/token-server/oauth/token
The Auth header is set in the API call using the access token from the token server:
Authorization: Bearer <access-token>
Token timeout: 36000 seconds
---------------------------------------------------------------------------------------------------------confluence.isys.no/display/FB/Autentisering
Client ID: anw_test
Secret is not sent in this mail. Sender is responsible for supplying you with this separately.