We have configured Kerberos in Documentum REST 7.3. For requests to REST, where users exists in AD, everything works fine. User (through some client) accesses REST and is automatically logged in.
Now, consider a scenario where user accessing the REST services does not exist in AD. The expectation would be that some kind of error message is send back in response so that it can be appropriately handled by the client.
However, the behavior we are seeing is as follows -
1. User (who does not have exist in AD/Documentum) calls REST service, say http://myserver/dctm-rest/repositories/myrepo/currentuser.xml
2. Browser shows a page can't be displayed message to the User.
3. On looking at the Network tab, it seems the request has been aborted. This is how the request/response looks like
Do we need to do any changes to Documentum REST so that instead of aborting the request, it gives some error message which can be handled by the client. We are trying to implement behavior very similar to what D2 does, that is, if user is not able to login using Kerberos, it redirects user to the login page. But for that we need a way to find that Kerberos login did not succeed (either due to user not existing in AD/Documentum or some other reason).
