Project Login (Sync)
Project Login Webhook makes it easy to add an extra security level by getting real-time information from another system if an agent has the appropriate rights to log in to a specific project. The success is either “true” or “false”, encoded in JSON.
In the response JSON object, each project indicated with a projectID needs to be true if the access is granted to an agent, otherwise it is false. If an agent has no access right to at least one project (that is: “false” answer arrived), the system does not allow the agent to log in, and the denied projects will be shown in a pop-up window.
Note: If you set the request method to GET, Webhook parameters are sent in HTTP query parameters. In all other cases (POST or PUT), Webhook parameters are sent in an HTTP body.
Warning: If server side is not well prepared, agents’ login is rejected.
Table of Contents
Request Object
Name | Type | Comment |
---|---|---|
customData | object | Agent custom data object. |
groupId | integer | Agent group identifier. |
projectId | integer | Project identifier. |
secondaryProjectIds | array of integers | Secondary project identifier(s). |
userId | integer | Agent identifier. |
username | string | Agent username. |
Sample Request Body
{
"projectId": 1,
"userId": 2,
"username": "x",
"groupId": 2,
"customData": [],
"secondaryProjectIds": [2, 3, 4, 5]
}
Sample Response Body
{
"1": true,
"2": true,
"3": false,
"4": true,
"5": true
}
Comments
Can’t find what you need? Use the comment section below to connect with others, get answers from our experts, or share your ideas with us.
There are no comments yet.