80 likes | 200 Vues
In this training session, Shilen Patel from Duke University covers advanced provisioning techniques with Grouper's Provisioning Service Provider (PSP). Explore key command line options for calculating, syncing, and comparing provisioning for individual and bulk identifiers. Understand the importance of caching for performance, tuning cache settings, and configuring logging with log4j to monitor provisioning activities. Additionally, learn about error handling strategies to ensure successful provisioning operations, including incremental provisioning and handling errors effectively. Quiz included for knowledge reinforcement.
E N D
Grouper Training – Admin – Provisioning Service Provider (PSP) – Part 4 Shilen Patel Duke University This work licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.
Contents Command Line Options Caching Logging Error Handling
PSP Command Line Options • Options (subset) • calc - Calculate provisioning for an identifier. • diff - Determine provisioning difference for an identifier. • sync - Synchronize provisioning for an identifier. • bulkCalc - Calculate provisioning for all identifiers. • bulkDiff - Determine provisioning difference for all identifiers. • bulkSync - Synchronize provisioning for all identifiers. • Demo
PSP Caching • Caching adjustments in ehcache.xml are critical for performance especially for bulk provisioning. • Avoid repeated subject queries by tuning cache settings for: • edu.internet2.middleware.grouper.subj.CachingResolver.Find • edu.internet2.middleware.grouper.subj.CachingResolver.FindAll • edu.internet2.middleware.grouper.subj.CachingResolver.FindPage • edu.internet2.middleware.grouper.subj.CachingResolver.FindByIdentifier • edu.internet2.middleware.grouper.subj.CachingResolver.FindByIdOrIdentifier • maxElementsInMemory should be equal to or greater than the number of subjects that you have. • timeToIdleSecondsand timeToLiveSeconds are ideally set to the amount of time it takes the bulk provisioning to run.
PSP Logging • Logging is controlled via log4j.properties. • Default logging: # Provisioning : PSP (version 2.1+) log4j.logger.edu.internet2.middleware.psp = INFO # Provisioning : vt-ldap # log4j.logger.edu.vt.middleware.ldap = INFO # Provisioning : Grouper plugin to Shibboleth attribute resolver # log4j.logger.edu.internet2.middleware.grouper.shibboleth = INFO
PSP Error Handling • Incremental provisioning • Error handling is controlled by a property in grouper-loader.properties: changeLog.consumer.psp.retryOnError • true: If an error occurs on a change log event, continue to retry it until it succeeds. • false: If an error occurs on a change log event, ignore the failure and move on to the next change. This assumes that the bulk provisioning job will eventually correct the failure. • Grouper report will indicate failures. • Grouper diagnostics will also report errors if the PSP incremental job has not had a success in the last 30 minutes. • Bulk Provisioning • By default, PSP will resume on errors.
Quiz Click on the quiz link in the video description to reinforce your knowledge of this topic.
Thanks! • Further information: • Infosheets, mailing lists, wiki, downloads, etc.:www.internet2.edu/grouper • Grouper demo server:grouperdemo.internet2.edu/ • Grouper Online Training Home:spaces.internet2.edu/x/IIGfAQ This work licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.