Hi,
I'm reviewing the REST API to help a client convert their application to use REST. One big gaping hole is that there doesn't seem to be any way to impersonate a user. Currently, they have a web based application where the user authenticates elsewhere, and a service account proxies all requests to Content Server via the SOAP API. The application never hangs on to the user's credentials, so is only passing their email address as the user account to impersonate. This doesn't seem to exist in the REST API. I think they theoretically could do this using the OTDS REST API but I'm not 100% sure. A client application ideally should only have to talk to one API when dealing with Content Server though.
-Hugh