...
In grouper 2.3.0 (unpatched) and previous versions, the subject API was configured with a sources.xml . This needs to be converted to config 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.
Configuration
Sample sources.xml config
Code Block |
---|
<?xml version="1.0" encoding="utf-8"?> <sources> <source adapterClass="edu.internet2.middleware.grouper.subj.GrouperJdbcSourceAdapter"> <id>jdbc</id> <name>Example JDBC Source Adapter</name> <type>person</type> <init-param> <param-name>sortAttribute1</param-name> <param-value>LOGINID</param-value> </init-param> <init-param> <param-name>searchAttribute0</param-name> <param-value>searchAttribute0</param-value> </init-param> <internal-attribute>searchAttribute0</internal-attribute> <search> <searchType>searchSubject</searchType> <param> <param-name>sql</param-name> <param-value> select s.subjectid as id, s.name as name, (select sa2.value from subjectattribute sa2 where name='name' and sa2.SUBJECTID = s.subjectid) as lfname, (select sa3.value from subjectattribute sa3 where name='loginid' and sa3.SUBJECTID = s.subjectid) as loginid, (select sa4.value from subjectattribute sa4 where name='description' and sa4.SUBJECTID = s.subjectid) as description, (select sa5.value from subjectattribute sa5 where name='email' and sa5.SUBJECTID = s.subjectid) as email from subject s where {inclause} </param-value> </param> <param> <param-name>inclause</param-name> <param-value> s.subjectid = ? </param-value> </param> </search> </source> </sources> |
This needs to be converted to config 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.
Sample subject.properties config:
...