Employee Identity (EIAM)
Verify Callback URL
Identity Synchronization
When an enterprise administrator saves callback configuration information, BambooCloud IDaaS sends a verification event to the configured URL callback service to validate the legitimacy of the callback address.
# Interface Format
| Parameter | Reference |
|---|---|
| Request URL | https://{app_domain}/callback |
| Request Method | POST |
| Request Header | Authorization: Bearer {access_token} |
# Request Parameters
| Parameter Name | Type | Description |
|---|---|---|
| nonce | String | Random number, used in combination with timestamp to prevent replay attacks. |
| timestamp | Integer | Timestamp, used in combination with nonce to prevent replay attacks. |
| eventType | String | Event type, the event type here is CHECK_URL. |
| data | String | When encryption is not enabled, a plaintext random string is sent. When encryption is enabled, an encrypted random string is sent. It needs to be decrypted to obtain the message content. After decryption, there are two fields: random and msg, where msg is the plaintext message content. |
| signature | String | Message signature. The signature calculation combines the signature key (signatureSaltValue) configured for the enterprise application, the timestamp, nonce from the request, and the encrypted message body. |
# Response Parameters
| Parameter Name | Type | Description |
|---|---|---|
| code | String | Return code, 200 indicates success. For failure error codes, refer to Error Codes. |
| message | String | Description of the response result. |
| data | String | When encryption is not enabled, returns the plaintext random string from the request body. When encryption is enabled, decrypts the encrypted random string from the request body and returns the re-encrypted value of that random string. It needs to be decrypted to obtain the message content. After decryption, there are two fields: random and msg, where msg is the plaintext message content. |
# Request Example
- Request example without message signature and encryption enabled
{
"nonce": "bqVHvThFGooCRjSf",
"timestamp": 1573784783795,
"eventType": "CHECK_URL",
"data": "random string",
"signature": ""
}
1
2
3
4
5
6
7
2
3
4
5
6
7
- Request example with message signature and encryption enabled
{
"nonce": "jmgjjEAJbrMzWmUw",
"timestamp": 15093849585,
"eventType": "CHECK_URL",
"data": "jRqGWO08Tyuxq+ChqGFk7SiPCt6MgcUDvzP5CBYnD30=",
"signature": "K08yDiTEc094KoccOY+VYLQFxxQ="
}
1
2
3
4
5
6
7
2
3
4
5
6
7
# Response Example
Status Code: 200
Request Successful
- Response example without message signature and encryption enabled
{
"code": "200",
"data": " 2852325935078140700",
"message": "success"
}
1
2
3
4
5
2
3
4
5
- Response example with message signature and encryption enabled
{
"code": "200",
"message": "success",
"data": "u5GkfEdZC0EDvDldLWBK/w=="
}
1
2
3
4
5
2
3
4
5
