Hi,
While doing some POC work, we discovered a quirk of the Content Server Members API. When you go to specify the primary group, you need to specify the KUAF.ID for that group rather than the group name. So long as you plan on just creating your users in DefaultGroup (ID = 1001), not a big deal, but if you wanted your user's primary group to be anything meaningful, this can be problematic. I know that the rest of the civilized world uses OTDS and synchronized partitions that sync to AD/ADFS/LDAP, but on this project, we're mandated to use another system as our source of truth, hence our experimentation with various API's to create users and groups. I had been pushing the CS REST API to create users since the OTDS API is more complex and there is no documented way to create the user login-enabled in Content Server/OTDS and set their password (although SAML authentication is being worked on, we're a long way from there).
So my questions to the group are:
1) Is it on the road-map to allow CS REST member creation to use names instead of KUAF.ID (KUAF ID is only meaningful in Content Server, no where else);
2) If not, are there any guidelines for creating users via OTDS so that they are login-enabled and their passwords set?
Thanks
-Hugh
