1 Reply Latest reply on Nov 4, 2015 9:44 AM by dw0lf

How to use PicketLink with RedHat DS (389-ds server) with no entryUUID support?

dw0lf Nov 4, 2015 7:12 AM

Currently truing to make my configuration work with Redhat DS(389-server ds) and seems like there is no support for RFC 4530 entryUUID.

Is it so? At least from 389 I can't find such attribute. Is there some plugin for the server available witch can do the trick?

Or is there known workaround? I think there was some bug about this, but It's not clear where is it no? At least entryUUID is missed from schema on 389-server.

How one can make Redhat DS (389-server) working with PicketLink's entryUUID? #137 (No support for RFC 4530 entryUUID attribute) – 389 Project

1. Re: How to use PicketLink with RedHat DS (389-ds server) with no entryUUID support?

dw0lf Nov 4, 2015 9:44 AM (in response to dw0lf)

This bug is actually corrected in PLINK_2.7.0.Beta1 for working with system props, and in Beta2 to working with Configuration API, like so: ..... builder .named("default") .stores() .ldap() .uniqueIdentifierAttributeName("nsuniqueid") ..... With this configuration and 2.7.0.Final PL my 389-server(1.3.3.1) seems to work just fine.
Actions