Client OAuth2.0-based Onboarding Process
This table lists the high-level steps for setting up OAuth2.0 authentication and invoking the Juniper Service APIs.
Action |
Who? |
---|---|
Review the Juniper Service APIs license/Terms of Use. | Customer/Partner |
Open the firewall ports. | Customer/Partner and Juniper |
Generate and share the unique application ID with the Customer/Partner. This application ID must be provided in every API request JSON payload. |
Juniper |
Generate OAuth2.0 credentials (clientID, secret) and share with Customer/Partner. | Juniper |
Create a Customer/Partner profile in the Juniper API gateway with OAuth2.0 as the authentication mechanism. | Juniper |
Create APIs and assign the Customer/Partner profile. | Juniper |
Share the API endpoints along with token endpoint with the Customer/Partner. | Juniper |
Validate that the Customer/Partner can invoke the APIs by passing the Access token (which is obtained by request to token endpoint) in the Authorization header. | Customer/Partner |
Establish the Customer Source Identifier. | Juniper and Customer/Partner collaborate |
Specify to Juniper an email aliases that is to be used for providing Juniper to provide new secret that would need to be used when the time to rotate the secret arrives (once a year). | Customer/Partner |