• Type: Sub-task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 3.0.0-alpha1, 3.0.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      Context:
      See parent task.

      AT:

      • identity.type is optional on the collection add role API
      • on missing type the backend tries to resolve this as a userID first and if there is no such user tries to resolve it as groupId
      • if the id neither belongs to a user nor a group a 400 error is returned indicating the user or group does not exist

            Assignee:
            Unassigned
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: