Lab 1.7 - Onboard a New API

Organizations change. With this change, new APIs are introduced requiring modifications to the API Gateway. In this section you will learn how to add additional paths.

Task 1 - Verify no access to API

1. From Postman, select the request PATCH-Change User Password-JWT

2. Select the Authorization tab
3. Select the previously created User1 token from the Available Tokens dropdown

4. The Token field is now populated

5. Click Send
6. You receive a 403 Forbidden response status code because the the new API has not been published at the Gateway

Task 2 - Add the new API path

1. From the browser, navigate to API Protection >> Profile. Click Profile to modify the previously created API protection Profile (not the + Plus symbol)

2. Click API-Protection

3. Click Paths

4. Click Create

5. The URI /aduser/password
6. Select the Method PATCH
7. Click Add

8. Click Save

Task 3 - Test Access to the new path

1. From Postman, select the request PATCH-Change User Password-JWT

2. Select the Authorization tab
3. Select the previously created User1 token from the Available Tokens dropdown

4. The Token field is now populated

5. Click Send
6. You receive a 200 OK that the endpoint is now published.