It’s easy for digital information to become a lot to manage. Users often find themselves overwhelmed with usernames and passwords when required to submit login credentials each time they use an application—especially across multiple applications. These login verifications may conflict with the security policies of the corporation itself, or simply become an inconvenience for users; as such, many corporations turn to single sign-on (SSO) solutions.
This white paper explains how applications built on MarkLogic can be integrated with SSO solutions at the database layer in order to prevent passwords from being directly sent to MarkLogic. We hope to provide useful insight on how to take full advantage of MarkLogic’s flexible security features to better secure access authentication.