...
These variables are there for you to key off. Note: you should not start your variable names with "cu_grouper" since that namespace is for built in variablesTODO
| Variable name | Description |
|---|---|
| cu_grouperEnroll | true if the user clicked the enroll button, false if the user clicked the unenroll button (e.g. for email templates) |
| cu_grouperTurnOffManager | url variable if you do not want to see the manager panel |
Text config beans
These are a little misnamed, they are for text or for other decisions about the screen. Could be a boolean result. It is strongly encouraged to externalize text in the UI externalized text config
...
Every text bean returns a string, but if its "true" or "false" it will be interpreted as a boolean.
| Text type | Type | Description |
|---|---|---|
| canAssignVariables | boolean | if the screen allows variables to be assigned in the URL for testing. e.g. to simulate various users and see how the screen responds note: only allow trusted users to be able to do this. Only Grouper admins can do this by default |
| canSeeScreenState | boolean | if the screen state analysis should be displayed on the screen to help the user understand why access exists or not. By default only Grouper admins can see screen state. Note that more columns of the user environment will also display |
| canSeeUserEnvironment | boolean | if the user variables and results should display. By default group readers and updaters can see this. Note that these are abbreviated if the user cannoy also see screen state |
| emailBccGroupName | String | if there are emails and a group should be bcc'ed then return the group name here |
| emailBody | String | if there are emails then this is the body. Note you can have a template that is dynamic, or different templates in different scenarios |
| emailSubject | String | if there are emails then this is the subject. Note you can have a template that is dynamic, or different templates in different scenarios |
| emailToUser | boolean | true if an email should be sent to user. Note you can send under certain circumstances if you like |
| enrollButtonShow | boolean | true if the enroll button should show. Note that the user cant enroll if they dont have optin on the group |
| enrollButtonText | String | Button text of enroll button. Defaults to: Enroll |
| enrollmentLabel | String | Text above the enrollment button that shows the state of the enrollment or whatever else |
| header | String | The H1 of the page |
| helpLink | String | Link where the help button goes |
| instructions1 | String | Instructions at the top of the page |
| logo | String | Link for logo |
| managerInstructions | String | Instructions to appear for readers/updaters who are managing users in this group |
| unenrollButtonShow | boolean | true if the unenroll button should show. Note that the user cant enroll if they dont have optout on the group. Note that the enroll and unenroll button will not show at once |
| unenrollButtonText | String | Button text of unenroll button. Defaults to: Unenroll |
Azure membership
Configure an azure connection in grouper.properties
| Code Block |
|---|
grouper.azureConnector.myAzure.loginEndpoint = https://login.microsoftonline.com
grouper.azureConnector.myAzure.DirectoryID = 6c4dxxx0d
grouper.azureConnector.myAzure.client_id = fd805xxxxdfb
grouper.azureConnector.myAzure.client_secret = ******************
grouper.azureConnector.myAzure.resource = https://graph.microsoft.com
grouper.azureConnector.myAzure.graphEndpoint = https://graph.microsoft.com
grouper.azureConnector.myAzure.graphVersion = v1.0
grouper.azureConnector.myAzure.groupLookupAttribute = displayName
grouper.azureConnector.myAzure.groupLookupValueFormat = ${group.getName()}
grouper.azureConnector.myAzure.requireSubjectAttribute = PENNNAME
grouper.azureConnector.myAzure.subjectIdValueFormat = ${subject.getAttributeValue("PENNNAME")}@upenn.edu |
...