...
| Info |
|---|
Since the HTTP header keys are case-insensitive, PIPEFORCE will convert any incoming HTTP header key to lower case and uses its lower case representation internally. This helps to avoid confusions with pipeline headers, those these keys are case-sensitive. Therefore, the examples here always use the lower case HTTP key, even if you could also use other case styles if you want. |
...
At first you need to obtain the Bearer token from an exchange flow where the login credentials will be exchanged to a Bearer token.
Then, you can set the Bearer token like this:
| Code Block |
|---|
authorization: Bearer <token> |
Here is an example of how you can obtain the Bearer access token from the PIPEFORCE IAM service:
| Code Block |
|---|
export TOKEN_RESPONSE=`curl -X POST --location "https://iam-<ns>.pipeforce.net/auth/realms/<ns>/protocol/openid-connect/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=password&client_id=pipeforce&username=<username>&password=<password>&scope=pipeforce"`
export PIPEFORCE_ACCESS_TOKEN=`echo $TOKEN_RESPONSE | jq -r '.access_token'`
curl "https://hub-<ns>.pipeforce.net/api/v3/command/..." -H -H "authorization: Bearer ${PIPEFORCE_ACCESS_TOKEN}" |
RunAs Authentication​
This is not really an authentication method since it switches from an already , successfully authenticated user to another user in case the user has the permission to do so.
...