Infoland Flex - User synchronization
- Jo Dybdal (Deactivated)
- Tuan Minh Nguyen
For the user to be able to login, he or she needs to have a user in our system. You need to implement a synchronization between our systems. A user will have a organisation and a department:
Organization
Departments
…
Users
….
If you do not have a synchronization already, you can use our api here: swagger
Use http methods POST, PUT and DELETE to do the intended actions.
POST = create
PUT = update / activate
DELETE = deactivate
Departments
{
"id": "some-unique-department-id"
"name": "Some Department",
"email": department@email.com,
"organizationId": "some-unique-organization-id",
"address": "Osloveien 10",
"postalCode": "1234",
"phone": "12345678"
}Name | Description |
|---|---|
| The id of the department, this needs to be unique for all departments. You should use a combination of multiple things, example: AMB(ambita)DNB(DNB)VE(Vest) = AMBDNBVE Or it could be a generated UUID, but we recommend the first example, since its easier to lookup. |
| Name of the department |
| Email of the contact person in the department |
| The id of the organization, this is added on creation of the organization by Ambita. This will be sendt to you during onboarding of new customers. We will be using similar logic as for the department id example: AMB(ambita)DNB(DNB) = AMBDNB |
| Address of the department |
| Postal code of the department |
| Phone number of the department. Only norwegian phone numbers. |
*All fields are required
Users
{
"name": "Ola Nordmann",
"username": "USERNAME",
"departmentId": "some-unique-department-id",
"email": "ola@nordmann.no",
"phone": "12345678"
}Name | Description |
|---|---|
| Name of the user |
| Username of the user, this needs to be unique for all users. We recommend using a pattern like this to prevent duplication errors: USERNAME@ORGANIZATION_ID = ola@AMBDNB |
| The id of the department |
| Email of the user |
| Phone number of the user. Only norwegian phone numbers. |
*All fields are required
Â