Jump to: navigation, search

Difference between revisions of "CDO/Net4j Authentication"

< CDO
(CDO 3.0)
 
Line 17: Line 17:
  
 
===CDO 3.0===
 
===CDO 3.0===
Note that in CDO 3.0 we have an additional, superior athentication
+
Note that in CDO 3.0 we have an additional authentication mechanism per CDOSession (not on Net4j IConnector level). Using the IConnector based authentication is not the recommended way anymore.
mechanism per CDOSession (not only on Net4j IConnector level). Search
+
this newgroup for "authen..." if you need hints.
+
  
Using the IConnector based authentication is not the recommended way anymore. The new CDOSession based approach envolves settingan IUserManager into the ISessionManager of the IRepository. Unfortunately (IIRC) you currently need to use internal code to do this. I'll change this if you filea bugzilla. On the client side you need to set an ICredentialsProvider into the CDOAuthenticator of the CDOSessionConfiguration. Bothe the IUserManager and the ICredentialsProvider can be the same implementations that you used with the Net4j based approach before.
+
The new CDOSession based approach involves setting an IUserManager into the ISessionManager of the IRepository '''before''' the repository is activated. On the client side you need to set an ICredentialsProvider into the CDOAuthenticator of the CDOSessionConfiguration '''before''' the session is opened. Both the IUserManager and the ICredentialsProvider can be the same implementations that you used with the Net4j based approach before.
  
CDO 3.0 does not have permission based security / Access Control List. But you might be able to implement your own using custom <tt>IRepository.ReadAccessHandler</tt> and <tt>IRepository.WriteAccessHandler</tt>.
+
CDO 3.0 does not yet have permission based security / Access Control List. But you might be able to implement your own using custom <tt>IRepository.ReadAccessHandler</tt> and <tt>IRepository.WriteAccessHandler</tt>.
  
 
===CDO 4.0===
 
===CDO 4.0===

Latest revision as of 02:31, 26 May 2011

In most enterprise application a user has to authenticate against the webserver, CDO application are not different in this aspect. So naturally CDO and Net4j provide a possibility to authenticate. The source code shown in this section is part of a big example project exploiting RCP + EMF + Databinding features.

Server

Server configuration with cdo-server.xml

Property-File based Authentication

If you are configuring your server using cdo-server.xml and providing authentication against a simple text file is as simple as uncommenting the following lines:

<acceptor type="tcp" listenAddr="0.0.0.0" port="2036">
  <negotiator type="challenge" description="/tmp/users.db"/>
</acceptor>

The value is the path to the user/password-File the authentication is done against. In this simple case the file is a Property-File and looks like this:

tom=myverysecretpassword

CDO 3.0

Note that in CDO 3.0 we have an additional authentication mechanism per CDOSession (not on Net4j IConnector level). Using the IConnector based authentication is not the recommended way anymore.

The new CDOSession based approach involves setting an IUserManager into the ISessionManager of the IRepository before the repository is activated. On the client side you need to set an ICredentialsProvider into the CDOAuthenticator of the CDOSessionConfiguration before the session is opened. Both the IUserManager and the ICredentialsProvider can be the same implementations that you used with the Net4j based approach before.

CDO 3.0 does not yet have permission based security / Access Control List. But you might be able to implement your own using custom IRepository.ReadAccessHandler and IRepository.WriteAccessHandler.

CDO 4.0

See Bugzilla 277075: Access Control system in CDO.

Client

IManagedContainer-Setup

The standard code to retrieve the session in an IManagedContainer looks like this:

public CDOSessionProvider {
  public CDOSession openSession(String id, String host, String port) {
    IConnector connector = TCPUtil.getConnector(IPluginContainer.INSTANCE, host + ":" + port );
    CDOSessionConfiguration configuration = CDOUtil.createSessionConfiguration();
    configuration.setConnector(connector);
    configuration.setRepositoryName(id);
 
    return configuration.openSession();
  }
}

And use it in our code like this:

CDOSessionProvider pv = new CDOSessionProvider();
pv.openSession("MyRep","localhost","2036");

The authentication negotiation has to be configured before the connection to the server is establish which happens here in the TCPUtil.getConnector()-method. So we somehow have to configure the system in between the call.

The only thing we need to do is to register a PostProcessor for the IPluginContainer.INSTANCE. This has to done only once for a IManagedContainer so the best part is a static block in the CDOSessionProvider.

static {
  PasswordCredentialsProvider credentialsProvider = new PasswordCredentialsProvider("tom", "blabla");
  IPluginContainer.INSTANCE.addPostProcessor(new ConnectorCredentialsInjector("localhost:2036",credentialsProvider));
}

Now your client authenticates against your CDO-Server and you'll receive a "org.eclipse.net4j.connector.ConnectorException" if you try to access session informations.


Resources

  1. Bugzilla 277075: Access Control system in CDO
  2. Authentication OK, but what about authorization
  3. CDO authentication