Page 3 of 11. Showing 108 results (0.07 seconds)
Subject API security by realm
). <init-param> <param-name>dbTableOrView</param-name> <param-value>tf_person_source_v</param-value> </init-param> <init-param> <param-name>realm__admin__dbTableOrView</param-name> <param-value>tf_person_source_admin_v</param-value> </init-param> Then you need to createUniversité Lille1
> <param> <param-name>filter</param-name> <param-value> (& (mail=%TERM%) (objectClass=supannPerson)) </param … (typeMember)) { label = label + " - " + typeMemberF; } return label; } Ne pas oublier de déclarer l'attribut concerné dans le sources.xmlSubject Identifier column in member table
identifiers. You can store any subject attribute in this column using the sources.xml configuration. Here's an example: <!-- subject identifier to store in grouper's member table --> <init-param> <param-name>subjectIdentifierAttribute0</param-name> <param-value>uid</param-value> </init-param> SyncGrouper changes v2.1
minutes: ws.client.user.group.cache.minutes = 5 df Subject API v2.1.1: Add this for ldap or jndi sources in the sources.xml <init-param> <param-name>SubjectID_formatToLowerCase</param-name> <param-value>false</param-value> </init-param> Grouper Client v2.1.2: Mergesources-comanage-template.xml
>UNIQUE_ID</id> <name>SOURCE_NAME</name> <type>person</type> <init-param> <param-name>jdbcConnectionProvider</param-name> <param-value>edu.internet2.middleware.subject.provider.C3p0JdbcConnectionProvider</param-value> </init-param> <init-param> <param-name>maxActive</param-name> <param-value>16</paramsources-comanage-template.xml
>UNIQUE_ID</id> <name>SOURCE_NAME</name> <type>person</type> <init-param> <param-name>jdbcConnectionProvider</param-name> <param-value>edu.internet2.middleware.subject.provider.C3p0JdbcConnectionProvider</param-value> </init-param> <init-param> <param-name>maxActive</param-name> <param-value>16</paramsources-comanage-template.xml
>UNIQUE_ID</id> <name>SOURCE_NAME</name> <type>person</type> <init-param> <param-name>jdbcConnectionProvider</param-name> <param-value>edu.internet2.middleware.subject.provider.C3p0JdbcConnectionProvider</param-value> </init-param> <init-param> <param-name>maxActive</param-name> <param-value>16</paramsources-comanage-template.xml
>UNIQUE_ID</id> <name>SOURCE_NAME</name> <type>person</type> <init-param> <param-name>jdbcConnectionProvider</param-name> <param-value>edu.internet2.middleware.subject.provider.C3p0JdbcConnectionProvider</param-value> </init-param> <init-param> <param-name>maxActive</param-name> <param-value>16</paramGrouper v2.5 customize UI security headers
</async-supported> <!-- these are defaults --> <!-- <init-param> <param-name>hstsEnabled</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>antiClickJackingEnabled</param-name> <param-value>true</paramMigrating from the Grouper JDBC subject source to the JDBC2 subject source
in subject.properties: subjectApi.source.floridaPerson.types Source param name: 'searchAttribute0' has value: 'description_lower' - configured in subject.properties: subjectApi.source.floridaPerson.param.searchAttribute0.value Source param name: 'dbUser' has value: 'pcdadmin' - configured in subject.properties