strange Behavior of PicketLinkIDMOrganizationServiceImpl

[j.harm]

Hi,

the class org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl (GateIn 3.2.0, JBossAS 5.1) works not as expected. If I use the standard configuration and set the option "ignoreMappedMembershipType" to true there will be no identity objects created in the database table "jbid_io". Deleting the option "associationMembershipType" it works as expected (even if "ignoreMappedMembershipType" is set to true or false).

If I configure PicketLink to use a FallbackIdentityStoreRepository with a readonly LDAP IdentityStore just holding users and some attributes (PicketLinkIDMOrganizationServiceImpl configured with "ignoreMappedMembershipType" set to false and "associationMembershipType" set to "member") the manager memberships are stored in the database but are not shown in the membership list of a user. Deleting the option "associationMembershipType" I get a "HTTP Status 403" after login. The database content looks okay.

I don't know if this is a problem of PicketLinkIDMOrganizationServiceImpl or a problem of PicketLink itself.

Kind regards,

Joerg

[bdaw]

What is the root of your problem? What kind of config are you actually trying to achieve?

[j.harm]

Hi Boleslaw,

I want to get the users from a readonly LDAP and the to store the groups and mamberships in the database. The users configured in organization-configuration.xml are stored in the database. The attached configuration works but the "manager" memberships are not shown in the membership list of a user.

Kind regards,

Joerg

[bdaw]

Actually which GateIn version are you using for this? I remember there were some fixed JIRAs that could be related - could you try with GateIn trunk?

[j.harm]

Hi Boleslaw,

we use GateIn 3.1.0-GA (not 3.2.0 as I wrote in my first post). If I find the time I will try it with the GateIn trunk.

Kind regards,

Joerg