Safewhere Identify 5.18 - Known issues

This document summarizes known issues and workarounds where available.

Removal of NemID authentication

When a user imports data containing NemID authentication, an error message "pluginType is invalid" will appear. This occurs because NemID is no longer supported due to redundancy. You can ignore this error; applications using NemID authentication will still be imported successfully.

Reversed display and value properties in group response of User REST API endpoints

There is a known issue with the REST API response for the groups within a user object, where the display and value properties are reversed.

• Current groups response within a user object is as follows:

{
  "schemas": [
    "urn:scim:schemas:core:1.0",
    "urn:scim:schemas:extension:enterprise:1.0",
    "urn:scim:schemas:extension:safewhere:identify:1.0"
  ],
  "userName": "user1",
  ...
  "groups": [
    {
      ...
      "display": null,
      "value": "[name of the group]",
      ...
    }
  ],
  ...
}

• The correct response according to the SCIM group schema should be:

{
  "schemas": [
    "urn:scim:schemas:core:1.0",
    "urn:scim:schemas:extension:enterprise:1.0",
    "urn:scim:schemas:extension:safewhere:identify:1.0"
  ],
  "userName": "user1",
  ...
  "groups": [
    {
      ...
      "display": "[name of the group]",
      "value": "[id of the group]",
      ...
    }
  ],
  ...
}

We will correct this issue in a future version.