Hello,
I have the example of an api that uses basic auth login endpoint (https://apis.server/v2/login) that gives a response like this:
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiJiM2EyNjk1Ny00NjEwLTQ1MTctYTJjNi1iNzRlNmZhZDYwOTYiLCJ1c2VyTmFtZSI6InBhcmFsbGVsX2dsYSIsImdyb3VwSWQiOiJhNDFjMjU2Yi1kNGM3LTRiYzEtOTA5Mi1jM2FkZWQ5YzM5MWMiLCJpYXQiOjE3MjYyMzQ4OTAsImV4cCI6MTcyNjMyMTI5MH0.cU8JVgIpC3zW7B2NwYf0pKYkOs59gocgsmyz1GYGjVY",
"refreshToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiJiM2EyNjk1Ny00NjEwLTQ1MTctYTJjNi1iNzRlNmZhZDYwOTYiLCJ1c2VyTmFtZSI6InBhcmFsbGVsX2dsYSIsImdyb3VwSWQiOiJhNDFjMjU2Yi1kNGM3LTRiYzEtOTA5Mi1jM2FkZWQ5YzM5MWMiLCJpYXQiOjE3MjYyMzQ4OTAsImV4cCI6MTcyODgyNjg5MH0.KptZZGbygQJHS6sfmz_Px8FU3umXbdkyGL_UoaZdDuI"
}
Then I have to use that token with the tag in the header: x-authorization-token
For these cases in other developments, I have used OAuth 2.0 with client credentials (example : https://community.infor.com/infor-developers/f/api-usage/34553/api-gateway---external-api-basic-auth-for-one-endpoint-and-bearer-token-for-methods/90756#90756 )
But if I do the same example, in this case it seems that it does not receive the parameters correctly:
{
"_original": {
"userName": "?w^~)?"
},
"details": [
{
"message": ""password" is required",
"path": [
"password"
],
"type": "any.required",
"context": {
"label": "password",
"key": "password"
}
}
]
}
But if I test with a Basic Auth type Endpoint, pointing to the Login URL, I obtain the token correctly by testing via Proxy:
Since I cannot handle the OAuth 2.0 login, or at least I try not to, there is a way that in my flows I can point to the Login Endpoint with Basic Auth, and then pass the token as an API Key with the tag x-authorization-token in the following GET/POST?
Is there a way to pass parameters to a CustomerAPI Endpoint for requests from an initial login Get?