Authentication to a different host

This system uses two-step authentication, but the token request is sent to a different host than the system the adapter integrates with — for example, a standalone single sign-on (SSO) service that returns a token valid for multiple downstream systems.

Configuration

This scenario requires only a change to action.json in the endpoint configuration at /adapter-home-dir/entities/.system.

action.json

Add an sso object to the getToken action. The sso object overrides the host, protocol, and port for the token request only, replacing the values from the service instance configuration or callProperties. The protocol and port can be omitted if they are the same as the adapter’s configured values.

1
{
2
  "name": "getToken",
3
  "protocol": "REST",
4
  "method": "POST",
5
  "entitypath": "{base_path}/{version}/authentication/login",
6
  "requestSchema": "tokenReqSchema.json",
7
  "responseSchema": "tokenRespSchema.json",
8
  "timeout": 0,
9
  "sendEmpty": false,
10
  "requestDatatype": "JSON",
11
  "responseDatatype": "PLAIN",
12
  "headers": {},
13
  "sso": {
14
    "protocol": "https",
15
    "host": "tokenhost",
16
    "port": 443
17
  },
18
  "responseObjects": [
19
    {
20
      "type": "default",
21
      "key": "",
22
      "mockFile": "mockdatafiles/getToken-default.json"
23
    }
24
  ]
25
}