Tuesday, March 10, 2015

An Example of Unsecure Architecture Decision

There is a great help topic regarding the Auto Login feature in the eDOCS DM 10 documentation:


"The eDOCS DM Auto Login feature is based on the client side knowing that the current user has already been authenticated on the local workstation; because of this, the eDOCS DM relative authentication does not require the user to re-enter a password. This means that the user’s password is not available on the server side when the eDOCS security token is being constructed."

Simply put it says that when the Auto Login feature is enabled, it is a DM client application that is responsible for user authentication, not the server.



If you grasped the idea and you liked it, you may also enjoy reading The Final Circle of Paradise book.

No comments:

Post a Comment