Grouper groups, memberships, and stems may be provisioned using the provisioning service provider (PSP, formerly known as LDAPPC-NG).
The PSP serves as an (incomplete) SPMLv2 provisioning service provider, which provisions objects to targets. Objects consist of identifiers, attributes, and references to other objects. Group memberships may be considered to be references. This diagram shows where the PSP fits in the Grouper architecture.
Provisioned objects are calculated from source data returned by the Shibboleth Attribute Resolver. The Shibboleth Attribute Resolver accepts many data connectors (sources), including LDAP, RDBMS, and Grouper.
The psp provisions targets using a standard provisioning language, SPMLv2. An SPMLv2 to ldap connector is provided, based on VT Ldap. Provisioning non-LDAP targets requires a target specific connector, for example, SPMLv2 to RDBMS.
Currently, the psp supports SPMLv2 requests represented as java objects via the Oasis SPMLv2 implementation. The requester is Grouper's cli, gsh.
The psp may be run using GrouperShell (gsh).
To provision, polling every 60 seconds for changes :
bin/gsh.sh -psp -bulkSync -interval 60
To calculate how an object should be provisioned :
bin/gsh.sh -psp -calc stem:groupName
Calculate provisioning for all identifiers.
Determine provisioning difference for all identifiers.
Synchronize provisioning for all identifiers.
Calculate provisioning for an identifier.
Determine provisioning difference for an identifier.
Synchronize provisioning for an identifier.
Provisioned object or schema entity id. For example, group, member, etc.
Number of seconds between the start of recurring provisioning iterations. If omitted, only one provisioning cycle is performed.
Path to configuration directory.
Log SPML requests and responses.
Print SPML responses to output file. Defaults to stdout.
Print SPML requests as well as responses.
SPML request identifier.
Return data (identifier and attributes).
Return everything (identifier, attributes, and references).
Return identifier only.
-diff <id>, or
-sync <id> must be specified. All other arguments are optional.
Calculate how an object should be provisioned.
Upon receipt of a
calc request, the psp will calculate how an object (or objects) should be provisioned, and will return a
calc response representing the correct provisioning.
Determine the changes necessary to transform a provisioned object from how it is currently provisioned to how it should be provisioned.
Upon receipt of a
diff request, the psp first performs a
calc request to calculate how objects should be provisioned. Then, the PSP queries each target to determine how objects are provisioned. The psp returns a
diff response representing the changes necessary to synchronize the provisioned objects from how it is currently provisioned to how it should be. The changes consist of add, delete, and or modify requests.
Synchronize a provisioned object.
Upon receipt of a
sync request, the psp first performs a
diff request to determine provisioning changes. Then, the PSP requests targets to perform the changes, and returns the results as a
Bulk requests operate on all configured source identifiers, and includes the remove of orphan objects (provisioned objects for which no source identifier is known).
LDAPPC-NG -> PSP
The code formerly known as "ldappc-ng" has been refactored to "psp".
The provisioning service provider and provisioning engine.
Distribution package for Grouper.
Example configuration and junit test modules.
Grouper change log integration including data connectors and change log consumer.
Grouper and LDAP integration including attribute definitions to transform Grouper names to LDAP DNs and vice versa.
Data connectors which return the identifiers of all Grouper groups, stems, and members.
Grouper provisioning target.
LDAP provisioning target.
Real-time provisioning is the provisioning of groups, stems, and memberships triggered from the Grouper change log. In Grouper 2.1 real-time incremental provisioning is available using the PSP. Real-time full provisioning is not yet available. Incremental provisioning is distinguished from full provisioning in that only a single or subset of an attribute's values are provisioned.
Real-time provisioning is available from the provisioning service provider as of Grouper 2.1.0. It should be possible to install and configure the PSP for Grouper versions 1.6 and up.
These instructions assume that Grouper subjects are already provisioned to your LDAP directory, and makes use of the vt-ldap based ldap source adapter.
Known Issues with "Real Time" Provisioning
- The PSP will run the shibboleth attribute resolver for every entry in the changelog including entries for which it will eventually do nothing. This is done because the Shibboleth Attribute Resolver is setup to resolve all attributes prior to returning the data for further evaluation.
- You cannot create an empty group to be incrementally provisioned. The groupOfNames schema that most LDAP and AD setups use REQUIRES at least one member. In practice, this means that you must add a member to a group within about 45 seconds of creation of that group or provisioning (and subsequent updates) will fail for that group. The only way to fix a group broken in this manner is to sync that group manually via
gsh -psp -sync group:that:is:broken. After running that command, the PSP will resume incrementally maintaining the group.
- Grouper API (requires Java 6 and a database, details are here)
- provisioning service provider (PSP)
- LDAP directory
Install : Grouper Installer
To install Grouper including the API, UI, WS, grouperClient, psp, etc., download and run the Grouper Installer.
As of Grouper 2.1.0, the PSP may be installed but not configured via the Grouper Installer.
java -jar grouperInstaller.jar
Install : Manual
Install the provisioning service provider by copying jar files and example configuration files from the psp distribution to your Grouper API installation.
Many jars are dependencies of the Shibboleth attribute resolver and may not be necessary in your deployment.
To install manually, download and unpack the psp, then copy jars and configuration files to your Grouper API installation.
Install : Manual - Download and Unpack the PSP
Download the PSP here and unpack.
The distribution name is of the form
tar xzf grouper.psp-2.1.0.tar.gz
Install : Manual - Copy Jars
Copy jars located in
lib/custom from the PSP distribution to the Grouper API installation.
cp -vR grouper.psp-2.1.0/lib/custom/ grouper.apiBinary-2.1.0/lib/custom/
Install : Copy Example Configuration Files
Copy example configuration files located in
conf from the psp distribution to the Grouper API installation.
Example psp configuration files are in directories named with the prefix
cp -vR grouper.psp-2.1.0/conf/ grouper.apiBinary-2.1.0/conf/
Configuration Example : Grouper to LDAP
This configuration example should apply to any ldap directory server.
Configuration Example : Grouper to Tivoli
This configuration example targets an IBM Tivoli Directory Server with requirements from Penn State.
member subject ids
Configuration Example : Grouper to OpenLDAP
This configuration example applies to OpenLDAP, and includes provisioning the
mailLocalAddress attribute sourced from the Grouper attribute framework.
For this example, new attribute framework
etc:attribute:seeAlso attributes will need to be created in Grouper. Here is example code using the Grouper API :
Configuration Example : Grouper to OpenLDAP MemberOf Overlay
This configuration example applies to an OpenLDAP directory with the memberOf overlay. This example is similar to the OpenLDAP example, except that the memberOf attribute is not provisioned by the psp.
Configuration Example : Grouper to OpenLDAP Multiple
This configuration example provisions multiple OpenLDAP directories, and is based on a request from the University of Modena and Reggio Emilia on the firstname.lastname@example.org mail list.
This configuration example provisions two OpenLDAP directories identically while provisioning groups only to a third directory.
Grouper LDAP subjects are sourced from the identical directories allowing for failover.
Because multiple directories are provisioned, this example is different than those which provision a single target. In the examples which provision a single ldap target, a single ldap connection is used to lookup Grouper subjects as well as to provision. In this example, an ldap connection is created to provision each target.
The connections to the three provisioned ldap targets are defined in
All three targets are provisioned in a single thread, future work should allow for one thread per target.
Configuration Example : Grouper to Active Directory
A contribution from Sébastien Gagné, Université de Montréal.
Configuration Example : LDAP to Grouper
This example provisions groups, stems, and memberships from an ldap directory to Grouper.
Configure LDAP Provisioning Target
The LDAP provisioning target connection is configured in
Configure the default search base DN to match your directory :
Configure authentication and encryption :
Configure the default base DN (container) for people and groups :
Configure LDAP Provisioning Structure : Flat
flat structure all groups are provisioned under a single base DN (container ID). A
flat group's ldap RDN is its Grouper name or displayName.
flat LDAP structure and
name group RDN source attribute ID in
Configure LDAP Provisioning Structure : Bushy
bushy structure groups are provisioned hierarchically, with stems as branches (ldap organizationalUnits) in the tree. A
bushy group's RDN is its Grouper extension or displayExtension.
bushy LDAP structure and
extension group RDN source attribute ID in
Configure LDAP Base DNs
The example default base DN is
dc=example,dc=edu. Change the base DN in
as well as
Configure LDAP Subject Source
Configure Grouper to look for subjects in your LDAP directory by using the ldap source adapter.
The Grouper LDAP subject source connection is defined in
Configure LDAP Subject Source ID Other Than "ldap"
The id of the Grouper LDAP subject source adapter,
<id>ldap</id>, appears in several psp configuration files. If your Grouper LDAP subject source adapter id is not "ldap", you should read the following and make changes to your psp configuration files. In the following examples, the Grouper LDAP subject source id has been changed from "ldap" to "ad".
In the psp service configuration
psp-services.xml, the LDAP target to be provisioned re-uses the same pooled vt-ldap connection as the Grouper LDAP subject source adapter. The value of the vt-ldap pool id property
ldapPoolId="ldap" should match the Grouper LDAP subject source adapter id
sources.xml. If your Grouper LDAP subject source id is
<id>ad</ad>, then the vt-ldap pool id should be
Also in the psp service configuration
psp-services.xml, the id of the LDAP target to be provisioned,
id="ldap", is the SPMLv2 targetId which should match the targetId attribute of
<identifier/> elements in the psp configuration file.
In the psp configuration file
psp.xml, the target id of the
<identifier/> element of objects to be provisioned,
targetId="ldap", should match the LDAP target id
<Service id="ldap"/> as defined in
psp-services.xml. If your Grouper LDAP subject source id is
<id>ad</id>, you do NOT need to change the targetId.
In the attribute resolver configuration
psp-resolver.xml, the Grouper LDAP subject source id,
<id>ldap</id>, appears in several elements.
The first place that Grouper LDAP subject source id "ldap" appears in the attribute resolver configuration is in the element which defines that the
MemberDataConnector should return the "dn" attribute for Grouper members whose subject source is "ldap". The "dn" attribute is used as the identifier of provisioned member objects. If your Grouper LDAP subject source id is
<id>ad</id>, then the source of the "dn" attribute should be
The second place that "ldap" appears in the attribute resolver configuration is in the element which defines that the "id" attribute should be returned as values of the "membersLdap" attribute for Grouper members whose subject source is "ldap". The values of the "membersLdap" attribute definition, Grouper LDAP subject ids, are used to calculate group memberships. If your Grouper LDAP subject source id is
<id>ad</id>, then the source of the "membersLdap" attribute should be
The third place that "ldap" appears in the attribute resolver configuration is in the element which defines that the "id" attribute should be returned as values of the "changeLogMembershipLdapSubjectId" attribute for Grouper members whose subject source is "ldap". The values of the "changeLogMembershipLdapSubjectId" attribute definition, Grouper LDAP subject ids, are used to calculate group memberships during processing of change log entries. If your Grouper LDAP subject source id is
<id>ad</id>, then the sourceId should contain "ad", for example,
Configure LDAP Subject Source in Grouper UI
ldap.properties from the Grouper API to the Grouper UI.
cp grouper.apiBinary-2.1.0/conf/ldap.properties grouper.ui-2.1.0/dist/grouper/WEB-INF/classes/
cp grouper.apiBinary-2.1.0/conf/sources.xml grouper.ui-2.1.0/dist/grouper/WEB-INF/classes/
vt-ldap.jar from the Grouper API to the Grouper UI :
cp grouper.apiBinary-2.1.0/lib/custom/vt-ldap-3.3.4.jar grouper.ui-2.1.0/dist/grouper/WEB-INF/lib
The Grouper UI will not load unless you edit
ldap.properties in your Grouper UI installation or copy
psp-ldap-target-2.1.0-SNAPSHOT.jar to your Grouper UI installation.
Comment out or remove the psp specific search result handlers in
ldap.properties in your Grouper UI installation :
Configure LDAP Subject Source in Grouper WS
Configure LDAP DNs Created from Grouper Names
A provisioned object requires a unique identifier. When provisioning an ldap target, provisioned object identifiers are ldap distinguished names (DNs).
psp-grouper-ldap project provides a Shibboleth attribute resolver attribute definition which maps Grouper names to ldap DNs.
Based on a request from the University of Montreal, the Grouper base stem to be provisioned may be omitted from ldap DNs. The following table describes the affect of the base stem to be provisioned when the structure is
grouper base stem
By default, the psp-example-* configuration files use the Grouper name to create ldap DNs. It is also possible to create ldap DNs from the Grouper displayName by changing the relevant sourceAttributeID to "displayName".
Configure Grouper Stem to be Provisioned
Configure the name of the Grouper stem to be provisioned, by default this is the root stem, which is the empty string.
The Grouper stem to be provisioned is configured in
Configure Grouper Change Log
The Grouper change log is configured in
To enable change log provisioning :
To schedule when the change log is processed :
To run full synchronizations periodically (by default every day at 5am) :
To run a full synchronization job at loader startup :
The Quartz cron string documentation is here.
Configure Grouper Logging
You may want to change the Grouper log file appenders in
Configure Grouper Versions Prior to 2.1.0
The following changes are necessary to support provisioning Grouper API versions prior to 2.1.0 with the psp.
1. For Grouper versions prior to 2.1.0, there is a bug which will throw a NullPointerException if the following is not present in
2. For versions prior to 2.1.0, the location of
ldap.properties specified in
sources.xml must be an absolute path. For versions 2.1.0 or later, the location of
ldap.properties may be an absolute path or in your Java classpath.
For example, Grouper API version 2.0.3 requires an absolute path to ldap.properties in
For Grouper UI and WS versions prior to 2.1.0, the path to
ldap.properties specified in
sources.xml will be different than in the Grouper API since the psp specific search result handlers must be commented out or removed in the Grouper UI :
3. For Grouper API versions prior to 2.1.0, the ldap source adapter in
subject.jar does not provide the method which allows the psp to re-use the same ldap connection as the subject source. You will need to copy
lib/grouper/subject.jar from the Grouper 2.1.0 API distribution to your pre-2.1.0 Grouper API installation.
Configure Subject API Cache
The Subject API cache is configured in
maxElementsInMemory to be greater than or equal to the number of subjects.
timeToLiveSeconds ... accordingly ... ?
Some words about testing via gsh.sh and looking at cache hit/miss ratio debugging.
As of Grouper version 2.1.0, which uses Ehcache 2.4,
statistics must be
"true" to collect statistics which are logged at
Configure PSP : Provisioning Service Provider
The psp configuration files are :
Configuration for the objects, identifiers, attributes, and references to be provisioned to a target.
Configuration for the Shibboleth attribute resolver.
Configuration for Shibboleth services such as the attribute resolver, psp, and provisioning targets.
Configure PSP : SPMLv2 Provisioned Objects, Identifiers, Attributes and References
The objects, identifiers, attributes, and references to be provisioned are defined in
Configure PSP : Provisioned Objects
Provisioned objects, or in SPMLv2 terms Provisioning Service Objects, consist of identifiers, attributes (probably), and references (maybe) to the identifiers of other objects, which are most likely located on the same provisioning target.
The following configures the psp to provision a
the unique id of the provisioned object
The id of an attribute resolver definition whose values are all source identifiers applicable to this provisioned object.
Configure PSP : Identifiers
Identifiers consist of a string ID, a target ID, and possibly a container ID. We consider a container ID to be similar to an ldap base dn. A container ID is itself an identifier, recursing potentially indefinitely.
The following configures the psp to provision the identifier of the
grouper object as an LDAP DN returned from the
groupDn Shibboleth attribute definition from
The id of the Shibboleth attribute definition whose value is an SPMLv2 PSO Identifier
The id of the provisioned target. Must match the id of a target configured in
The string id of the pso identifier containing the object.
The following is an identifier expressed in SPMLv2
The following is a identifier expressed in LDIF
Configure PSP : Identifying Attribute
<identifyingAttribute/> of a provisioned object has two purposes : (1) to determine the schema entity of target objects returned from a lookup or search request and (2) to be converted to a query when searching a target for all identifiers. If
<identifyingAttribute/> is not present, the provisioned object will be ignored during bulk requests.
(1) The provisioning service provider needs to map provisioned object identifiers to provisioned objects (schema entities).
For example, given a lookup request for the id "edu", the psp needs to know if "edu" is a group or a stem. Given the following configuration, if the provisioned object with id "edu" has an "objectclass" attribute with value "organizationalUnit", then the schema entity is "stem". If the provisioned object with id "edu" has an "objectclass" attribute with value "groupOfNames", then the schema entity is "group".
The psp evaluates all <identifyingAttribute/> elements, only one should match, otherwise an exception is thrown.
(2) In order to synchronize all objects during bulk[Calc|Diff|Sync] requests, the psp needs to know the identifiers of all provisioned objects (schema entities) on a target for which the psp is authoritative. The psp uses
<identifier containerId="..."/> elements to create SPMLv2 search requests.
For example, in the configuration example above, the psp will perform an ldap search with filter "(objectClass=organizationalUnit)" to retrieve the identifiers of all provisioned stems as well as an ldap search with filter "(objectclass=groupOfNames)" to retrieve the identifiers of all provisioned groups. The base of each search will be the containerId of the
Configure PSP : Alternate Identifier
<alternateIdentifier/> element configures the psp to rename provisioned objects. It refers to an attribute resolver definition whose value is the previous (old) identifier of an object after it has been renamed. If
<alternateIdentifier/> is not present, provisioned objects will not be renamed, instead the old object will be deleted and a new object created.
The id of the Shibboleth attribute definition whose value is the previous SPMLv2 PSO Identifier.
Configure PSP : Attributes
Name value pairs. Probably multi-valued. Case sensitive names and values. We return values in the same order as they were given to us.
The following configures the psp to provision the
cn attribute of a
group. The value of the
cn attribute is returned by the
cn Shibboleth attribute definition from
The following is an attribute expressed in SPMLv2
The following is a attribute expressed in LDIF
Configure PSP : References
A reference refers to the identifier of another object. It consists of two identifiers, the "from object" and the "to object". A node in a directed graph. Directional.
The following configures the psp to provision a reference from a
group to a
member as values of the
member attribute. The values of the reference are returned by the
membersGsa Shibboleth attribute definitions from
The following is a reference expressed in SPMLv2
The following is a reference expressed in LDIF
Configure PSP : Attribute Resolver
The values of the identifiers, attributes, and references to be provisioned are defined by a Shibboleth attribute resolver configuration
Configure PSP : Attribute Resolver and Grouper Integration
Please see Grouper and Shibboleth Integration.
Configure PSP : Attribute Resolver and Grouper ChangeLog Integration
Real-time provisioning based on the Grouper change log involves the transformation of change log entries into provisioning operations.
Provisioned objects, identifiers, attributes, and references are calculated by the Shibboleth attribute resolver from change log entries.
Please see Grouper and Shibboleth Integration for more information on the change log data connector.
The psp-grouper-changelog project provides a change log consumer implementation, edu.internet2.middleware.psp.grouper.PspChangeLogConsumer. Documentation for Grouper change log consumers is here.
Configure PSP : PspChangeLogConsumer
The PspChangeLogConsumer processes change log entries which match hardcoded change log actions and categories. A future version should allow for configuration via xml or property files.
The change log events currently handled are :
Configure PSP : Logging and Output
The psp is a Shibboleth service which is configured in
The psp uses slf4j, and with Grouper, log4j configured in
The path to the file to which SPML requests and responses are written.
Configure PSP : LDAP Target
The LDAP target to be provisioned is a Shibboleth service configured in
By default, the LDAP target to be provisioned re-uses the same
vt-ldap connection as the Grouper LDAP source adapter.
The path to the file to which SPML requests and responses are written.
Before you can provision anything from Grouper to ldap or anywhere else, you will need to create the corresponding objects in Grouper using the UI, API, GSH, WS, loader, import, etc.
Provision Grouper : GSH
To calculate how a group should be provisioned :
bin/gsh.sh -psp -calc edu:group
To diff the current and correct provisioning of a group :
bin/gsh.sh -psp -diff edu:group
To provision or synchronize a group :
bin/gsh.sh -psp -sync edu:group
Provision Grouper : Grouper Change Log
To provision in real-time triggered by the Grouper change log, enable the psp consumer in
and run the loader via
Real-Time Changelog Provisioning Details - Probably More Than You Ever Want to Know
Changes to grouper are consumed by change log consumers. Grouper change log consumers are managed by the grouper loader and are configured in
If you are familiar with an ldap server audit log which logs ldif entries, the grouper changelog is similar, sort of, except that it writes rows to a table.
Grouper change log consumers process change log entries. A change log entry consists of single-valued attributes. A change log entry is a java representation of a row in the change log table
For example, when a member is added to a group, the following is part of the psp log :
When a change occurs in grouper, a representation of that change is written to a temporary table
grouper_change_log_entry_temp. The grouper loader periodically (every minute) reads this table, performs magic like potentially updating the PIT (point-in-time auditing) tables, and writes to the
grouper_change_log_entry table. It also assigns a sequential number to each action.
Change log entries written to the
grouper_change_log_entry table are processed in order of sequence number by every change log consumer. The grouper loader persists the last sequence number successfully processed by each change log consumer.
Every minute, the grouper loader retrieves batches of 100 change log entries (
grouper_change_log_entry rows), terminating at a maximum of 100,000 change log entries. These batches of 100 change log entries are passed to each change log consumer.
Change log consumers must extend the ChangeLogConsumerBase class :
Each change log consumer must return the last sequence number processed. If a change log consumer wishes to retry the current change, it should return the current sequence number - 1.
The psp change log consumer is like any other grouper change log consumer in that it processes change log entries.
For each change log entry received, the psp change log consumer determines the change log category (for example "membership") and change log action (for example "addMembership") and either processes or ignores the change log entry. Supported change log categories and actions are coded in the psp change log consumer, take a look at the EventType enum in the PspChangeLogConsumer. To support a change log category and action that is not supported by the provided psp change log consumer, you will need to provide your own implementation, probably by extending the psp change log consumer class. For help, ask email@example.com.
Processing an "addMembership" change log entry results in a psp calc request, where the identifier (principal name) to be calculated is the change log sequence number :
The change log data connectors know how to retrieve a change log entry from grouper via the change log sequence number, and return attributes to the attribute resolver representing the change log entry. In general, the change log data connectors convert a grouper change log entry into (shibboleth attribute authority) attributes. For example, the attribute authority will return the following attributes for an "addMembership" change log event :
The values of the "changeLogMembershipGroupDn" and "changeLogMembershipMemberDn" attributes are identifiers for the "groupMembership" and "memberMembership" provisioned service objects configured in
The "groupMembership" provisioned service object in
psp.xml provisions the member attribute of a group calculated from an add or delete membership change log entry :
The "memberMembership" provisioned service object in
psp.xml provisions the memberOf attribute of a member calculated from an add or delete membership change log entry :
The next step in processing by the psp after resolving attributes via the attribute authority is to resolve references. The values of the "changeLogMembershipLdapSubjectId" and "changeLogMembershipGroupName" attributes are converted to identifiers by executing psp calc requests.
In the following example, the psp change log consumer resolves provisioned service object identifiers for the principal with name 'edu:groupA', and returns an ldap dn 'cn=groupA,ou=edu,ou=groups,dc=example,dc=edu' :
In the following example, the psp change log consumer resolves provisioned service object identifiers for the principal with name 'test.subject.1', and returns an ldap dn 'uid=test.subject.1,ou=people,dc=example,dc=edu' :
When provisioning ldap directories, the member dn is either retrieved via an ldap grouper subject lookup or via the grouper subject source cache.
After resolving reference identifiers, a calc response is finally returned by the psp for the calc request whose id is the change log sequence number. The calc response returned by the psp represents how an add or delete membership change log entry should be provisioned, for example :
The next step in change log entry processing by the psp change log consumer is to determine the difference between how each object should be provisioned (the calc response) and how each object is currently provisioned.
For example, for each reference that should or should not be provisioned for an add or delete membership change log entry, the psp change log consumer performs an spml 'hasReference' search. Of course, the spml 'hasReference' search must be supported by each provisioned target implementation.
In the following example, the object with identifier 'cn=groupA,ou=edu,ou=groups,dc=example,dc=edu' is queried for whether or not it has a 'member' reference to 'uid=test.subject.1,ou=people,dc=example,dc=edu' :
The search response is successful but does not contain any provisioned service objects, which means that the reference does not exist.
Because the reference that should exist does not, a modify request is executed by the psp to add a 'member' reference with id 'uid=test.subject.1,ou=people,dc=example,dc=edu' to the object with id 'cn=groupA,ou=edu,ou=groups,dc=example,dc=edu' :
Phew, done. In the above example, the psp has added a member to a group as a result of processing an add membership change log entry. It will also add the memberOf attribute to the member object, but I have omitted that xml.
For more detailed examples, take a look at the spml requests and responses in
src/test/resources of the various
Real-Time Provisioning Beta-Testing : Grouper Subject Sources
Number of Subjects
sAMAccountName (value same as cn)
Real-Time Provisioning Beta-Testing : Provisioning Targets
IBM Tivoli Directory Server
Sun Java System Directory Server Enterprise Edition 6.3.1
Active Directory, OpenLDAP
Real-Time Provisioning Beta-Testing : Provisioning memberOf
The groups that a member is a member of may be provisioned to the memberOf attribute. Some LDAP implementations, such as Active Directory, automatically maintain the memberOf attribute. OpenLDAP maintains the memberOf attribute automatically via the memberOf overlay. The value of the memberOf attribute is typically a group DN.
memberOf for members (people)
memberOf for groups
automatic (Active Directory)
automatic (Active Directory)
automatic (Active Directory), OpenLDAP+memberOf
automatic (Active Directory), OpenLDAP+memberOf
Real-Time Provisioning Beta-Testing : Provisioning eduMember
The eduMember objectClass defines the isMemberOf and hasMember attributes, whose values are identifiers which are not DNs.
Real-Time Provisioning Beta-Testing : Provisioning eduCourse
The eduCourse objectClass defines course related attributes.
Real-Time Provisioning Beta-Testing : Provisioning Structure
The group provisioning structure may be either
flat structure provisions all groups into a single container. A
bushy structure provisions groups hierarchically.
For example, the DN of a group with name 'edu:stem:group' in a
flat structure looks like :
while the DN of a group with name 'edu:stem:group' in a
bushy structure looks like :
Structure (flat or bushy)
Real-Time Provisioning Beta-Testing : Membership Structure
Given groupA with memberA and groupB with memberB :
If groupB is added as a member to groupA, how do you want groupA to be provisioned :
The everything membership structure handles applications which may not support nested groups and represents the nested structure of the group memberships.
The same membership structure applies to memberOf :
Excluding LDAP provisioning for groups based on group name
This is based on a contribution by NYU which has been integrated into the Grouper API - Selective Group Exclusion When Provisioning to LDAP
In grouper.properties, set:
Also, in grouper.properties, add the names that you want to exclude (regular expressions):
In the psp-resolver.xml, in each section (there are a few) that returns groups, subtract the following:
So for example, the following:
.. would instead become: