> drop-in REST API
> GET /user/:user/exists
Wat. Use HEAD. Seriously.
Also, what is ":user" - how do you define the way an account is found in the tree?
How do you handle complex trees with potentially conflicting values for the attribute you use as 'username' ?
Why are their dedicated endpoints for password, expiry, enable/disable/unlock. These are all just attributes on the user object.
> drop-in REST API
> GET /user/:user/exists
Wat. Use HEAD. Seriously.
Also, what is ":user" - how do you define the way an account is found in the tree?
How do you handle complex trees with potentially conflicting values for the attribute you use as 'username' ?
Why are their dedicated endpoints for password, expiry, enable/disable/unlock. These are all just attributes on the user object.