LDAP integration is (and was) working but I get the exception on the synchronisation at startup and if I try to change some role mappings.
I can see from the classes that org.apache.archiva.redback.rbac.ldap.LdapRbacManager$RoleImpl is NOT enhanced but org.apache.archiva.redback.rbac.jdo.JdoRole IS enhanced. Therefore the exception is feasible. But the question is: why is an implementation of a role created using the LDAP impl but not the JDO impl? As a child of <ldapConfiguration> <writable>false</writable> is set in archiva.xml. Regards, Alex -----Ursprüngliche Nachricht----- Gesendet: Mittwoch, 17 September 2014 um 22:24:36 Uhr Von: "Jonathan Sharp" <[email protected]> An: [email protected] Betreff: Re: ClassNotPersistenceCapableException: The class "org.apache.archiva.redback.rbac.ldap.LdapRbacManager$RoleImpl" is not Persistence-Capable. Hi Alex, I can't reproduce this. Perhaps the docs on LDAP config will help -- http://archiva.apache.org/docs/2.1.1/adminguide/redback-runtime-configuration.html#LDAP_configuration -Jon
