From: Scott Koranda email@example.com
Sent: Tuesday, January 10, 2017 6:18 AM
To: Hyzer, Chris <firstname.lastname@example.org>
Cc: email@example.com Mailing List <firstname.lastname@example.org>
Subject: Re: [grouper-users] grouper sources.xml conversion to subject.properties overlay configuration
Thank you for the enhancement and for the documentation.
Most of the Grouper deployments I work with use LDAP (ie.
JNDI) as the subject source as opposed to JDBC.
Would you consider adding more detail including a full example
for a "typical" JNDI source? I can provide you some example
sources.xml if you would like to see what I usually encounter
in my deployments.
I would also find it helpful to have every configuration
option enumerated, with any applicable default, if possible.
Lastly, a number of deployments that I work with use more than
one LDAP/JNDI subject source simultaneously. Can you document
how a deployer would configure N simultaneous LDAP/JNDI
sources? (I suppose it would be good to also document N
simultaneous JDBC sources too).
Thank you for your consideration.
> The sources.xml file is migrated to subject.properties overlays so Grouper
> packaging can have defaults and overlays. Also so the Grouper team can manage
> internal sources without having to merge with a potentially changed file.
> Long story short, you can install API patch #40. At this point you can still
> use sources.xml, or you can migrate to subject.properties.
> Run the latest 2.3.0 grouperInstaller.jar and convert your sources.xml to
> Everything is explained in the link above.
> Ps. in 2.4.0 you will be required to do this migration, so if you do it now you
> save a step for later…