Hello,
I've created Apigee Edge trial account using the link https://login.apigee.com/sign__up. Upon account activated, generated OAuth token using the below API.
POST https://login.apigee.com/oauth/token
Content-Type: application/x-www-form-urlencoded
Accept: application/json;charset=utf-8
Authorization: Basic ZWRnZWNsaTplZGdlY2xpc2VjcmV0
username=xxxx@yyyy.com&password=xxxx&grant_type=password
This return the access token response as below:
{ "access_token": "xxx",
"token_type": "bearer",
"refresh_token": "xxx",
"expires_in": 43199,
"scope": "scim.emails.read scim.me openid password.write approvals.me scim.ids.read oauth.approvals",
"jti": "3e7d31ff-3d85-41a3-8472-3b3e17f746e6"
}
Thus generated access token used for the API call
GET https://api.enterprise.apigee.com/v1/users
Authorization: Bearer xxxx
This resulted in response 403 Forbidden.
When tried the API call
GET https://api.enterprise.apigee.com/v1/organizations/{my_trial_account_organization_name_here}/users
Authorization: Bearer xxxx
Returned below response:
200 OK
[]
Could some please let me know why the admin user is not listed in the second API call and why the first API call is retuning 403 error?
The /users endpoint is only available for Apigee Edge Private Cloud, not the public cloud version.
For what you're trying to find you may find the following APIs useful
/userroles - to get list of user roles
/userroles/x/users- to get list of users associated with a role eg such as orgadmin
Thank you so much Dane for clarifying on the API availabilities.
Could you please let me know whether this limitation introduced recently?
I remember on month of August, 2020 we had done a POC on the same APIs and we were able to achieve the below listed operations:
Could you help me in understanding the difference in the behavior?