Wiko Connector
Introduction
Wiko Connector allows to create identities in the Wiko system using REST api.
Â
Manager Issue
There is field superior
which holds reference to user manager. To change it, the request has to contain username of superior. Our customer stores username in attribute and uses it this way. It works, but our normal configuration will not work as it will provision User-Id, not username. We will need to implement adjustment of username on-the-fly when we need it.
System Identity Types
There is Wiko User
type.
Attribute | Description |
---|---|
| The username of the user |
| Salutation (it can be different after provisioning depending on the language, so that the calculated attribute value is |
| Professional title |
| Â |
| Â |
| Â |
| Â |
| Not supported |
| Not supported |
| Â |
| Â |
| Â |
| Â |
| Â |
| User password. Used write-only. |
| Reference to user that is a superior. Please read note #Manager-Issue |
| Â |
| User language - (it can be different after provisioning depending on the language, so that the calculated attribute value is ' |
| Â |
| Â |
| Â |
| Â |
| Â |
| Â |
| |
| |
| |
| Â |
| Â |
| Â |
| Â |
| Write-only. Please check https://itsense.atlassian.net/browse/IMS-6383 for details. |
| Write-only. Please check https://itsense.atlassian.net/browse/IMS-6383 for details. |
System Resource Types
There is a System Resource Type
but it is used only to create dummy resource that can be assigned to Core Identities to create Identities.
System Parameters
Parameter | Mandatory | Example | Description |
---|---|---|---|
| The base url of the Wiko API endpoint | ||
| imex | Username used in authentication for API | |
| password | Password used in authentication for API |
Identity features
The following identity functions are supported:
Supported | |
Create / delete identities | |
Provisioning identities | |
Update identities          | |
Provisioning identity updates   | |
Deprovision identities  | |
Cleanup of inactive identities active     | - |
Check password changed active | - |
Resources features
The following resource functions are supported:
Supported | |
Create/delete resources | - |
Provision resources     | |
Update resources         | - |
Provisioning resource changes | - |
Deprovisioning resources         | - |
Provisioning resource allocations         | - |
Deprovisioning resource allocations     | |
Provisioning resources-resource allocations     | - |
Deprovisioning resource resource allocations   | - |
Â
Cleanup features
The following cleanup functions are supported:
Supported | |
In the should-actual Log available    | - |
Should be - Actually is - cleanup | - |
Read back account properties | - |
Resource identity member target system clean up | - |
Resource resource member target system clean up | - |
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.