|
This document refers to 1.1.x version of xCMIS. IntroductionCurrently, xCMIS uses authentication mechanism provided by the eXo organization service. This article shortly describes how to adopt this mechanism to necessary conditions or write own authenticator . DetailseXo organization service includes the following components: - ConversationState object which stores all information about the state of the current user; - Identity object, which is a set of principals to identify a user, stored in ConversationState; - An Authenticator is responsible for Identity creating and validating User; In case of need to write own authenticator, is good thing to write it as a container component. Basically, authenticator must contain two methods:
Example configuration might look like: <component>
<key>org.exoplatform.services.security.Authenticator</key>
<type>org.exoplatform.services.organization.auth.OrganizationAuthenticatorImpl</type>
</component>This example of configuration is located in exo.core.component.organization.api-*.jar at "/conf/portal/configuration.xml". As we can see, this is quite simple. It is up to the application developer (and deployer) whether to use the Authenticator component(s) and how many implementations of this components can be deployed in container. The developer is free to create an Identity object using a different way, but the Authenticator component is the highly recommended way from architectural considerations. For more detailed explanation & examples, please refer to http://wiki.exoplatform.com/xwiki/bin/view/Core/Security+Service wiki page. For more security configuration look at xCMISwithWCMconfiguration#Security |