Since the June release, K2 Cloud has started using Open ID Connect (OIDC) to authenticate and authorize users. With this change, the OAuth flow that used to be based on an Azure flow changed. Basic authorizations continue to function as they did before, but if you were using OAuth, or need to use OAuth in a new application that uses these APIs, you’ll need to configure Postman and/or your code to use the new client IDs and redirect URIs. This article describes how to retrieve the values you need to set up PostMan or configure an OAuth Resource for the K2 APIs.
There are two ways to retrieve the values you need to initiate an OAuth flow.
To find the client ID and redirect URI, follow these steps:
Once you have the values you need, set up the flow in Postman to test your API calls.
Open the Get New Access Token dialog in Postman and configure the following values
Your Postman dialog should look similar to the following
When you click Request Token, you’ll be prompted to log in and should receive a bearer token to use in your Postman requests