Include Page | ||||
---|---|---|---|---|
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
These topics are discussed in the "Grouper API" training series. |
Table of Contents |
---|
Building the Grouper API
...
Section | Configuration File | Purpose |
---|---|---|
grouper.hibernate.properties | integrating the Grouper API with the database that will house your Groups Registry | |
sources.xml | integrating the Grouper API with chosen identity sources | |
grouper.properties | defaults for Grouper privileges, enabling identified external users to act with elevated root-like privilege, changing the display name for internal subjects | |
log4jlog4j2.properties | logging | |
grouper-loader.properties | auto-load memberships from external sql sources, register notification consumers, validate Grouper Rules, update enabled/disabled flags, etc |
...
Grouper requires that all subjects must be explicitly granted access or naming privileges (cf. Glossary Grouper glossary), with one caveat. There is a special "subject" internal to Grouper called the ALL subject, which is a stand-in for any subject. The ALL subject can be granted a privilege in lieu of assigning that privilege explicitly to each and every subject.
...