The single sign-on framework can integrate other applications with the Contensis authentication system.
The benefit of single sign-on is that users have fewer logins to maintain and remember. This can also lead to a greater uptake of an intranet by staff.
Contensis provides a web service that can be called on by other applications to gather and edit user information. An administrative account must be used to access the web service. Typically, Contensis will pass a security token on the querystring to the application, and the application will then verify the security token using the webservice and react accordingly.
Single sign-on has been used in many integrations to provide a seamless transition from a Contensis-authenticated site through to any other application. Common integrations include active directory and our own who's who module. As it is a standards-based Soap service, any client, including Java, can be used to access it.
One of our customers, MCP plc, uses this service to transition users between their own web-based application and the help application for their product which is powered by Contensis. MCP is a Java house and has implemented the integration themselves, using our single sign-on documentation and, initially, a little technical consultation with one of our technical team.