We are currently working on integrating with the Apigee Edge APIs and need some clarification regarding the authentication flow described in the documentation.
As per the documentation, the token generation request requires the following Authorization header:
Authorization: Basic ZWRnZWNsaTplZGdlY2xpc2VjcmV0
The documentation also mentions that this value should be used exactly as provided and appears to be a hard-coded value required by the API.
We would like to better understand the following:
-
Is this Authorization header value a global static value that should always be passed as-is?
-
Or is this value expected to be generated/provided separately by the customer?
-
If this is a shared/static value, how does the API identify and authenticate the specific user or organization?
-
Are there any additional organization-specific parameters/scopes required during authentication?
We are currently testing the authentication flow using dummy credentials and are receiving the following response:
Request:
curl -X POST --data 'password=******&grant_type=password&username=******' \
-H 'Authorization: Basic ZWRnZWNsaTplZGdlY2xpc2VjcmV0' \
-H 'Accept: application/json;charset=utf-8' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-A 'Jersey/3.1.8' \
'https://login.apigee.com/oauth/token'
Response:
{
"message":"Encountered an exception due to response code 500 and message {\"signupX\":\"https://apigee.google.com/welcome\",\"passwd\":\"https://login.apigee.com/reset\",\"signup\":\"https://login.apigee.com/sign_up\"}"
}
Could you please help us understand whether this is the expected behavior/error response when invalid or dummy credentials are passed, or if this indicates any issue with the authentication request format itself?
We would appreciate any clarification on the expected authentication behavior and supported setup flow.
