...
Once a user registers based on email, then it is vetted that the email address that the user was invited by is a vetted email address. There is a column in the external subject table to hold a list of comma separated email addresses that are vetted. Currently this is not used for anything (i.e. it is not a subject attribute), however, if an admin wants to contact someone, these are email addresses that the user has responded to...
Admin audit emails
If you enable admin emails for invites in media.properties:
| Code Block |
|---|
#if admins should be emailed after each action, put comma separated addresses here
inviteExternalMembers.emailAdminsAddressesAfterActions = mchyzer@isc.upenn.edu
|
Then this email is sent to the admins after each invitation:
| Code Block |
|---|
-----Original Message-----
From: noreply@yourschool.edu [mailto:noreply@yourschool.edu] <-- this is configurable in grouper.properties
Sent: Monday, November 29, 2010 2:24 PM
To: Chris Hyzer
Subject: TEST:Grouper external person invitation
Hey,
The Grouper external subject invite screen was used by Subject id: GrouperSystem, sourceId: g:isa - GrouperSysAdmin
Email addresses to invite: someone@yahoo.com
Email addresses to notify once registered: inviter@school.edu
Email subject: test subject
Message to users: test body
Group Names (ID Path) to assign: etc:webServiceClientUsers
Group UUIDs to assign: 9662c7ee3e4d4e089a2ea8e376483601
Invitation expires on: 2010-12-06 14:24:16.826
Regards.
|
To do
- Add multiple search strings and sort fields based on new member columns
- Add back to admin UI link
- Link from group screens?
- Email audit to admins
- Expire things deleted for a certain period of time?
- Regular audit
- Input eppns directly (optional?)