Email sent to peer contacts #392
Description
When receiving an account request or account renewal request from external peers, I, as a peer contact, want the email to be as specific and actionable as possible.
Current issues
The current mail contains two sets of three links each, which allows me to log in and either handle request for known users or communicate with unknown users. That is already a bit much to decide on.
The reason for having three links per set is to account for the login methods, currently in the shown order:
- login as external user
- login with certificate
- login using OIDC
Concerns regarding login
Given that login options will vary from each instance, we should allow for scenarios where all options (and new to come) are available.
But if configuration are set to a limited set of options, then the mail sent out to peer contact, ideally, should reflect this.
Users will not necessarily know which option to choose, so it is likely that a user in doubt will click the first link of the three in each set. At UCPH we clearly want the OIDC option to be listed first (ie. reverse the order), and perhaps only that option (at least consider if we through configuration can decide to allow for external peers to accept other external peers or not).
Future initiatives of importance to this issue
The Where Are You From (WAYF) project will address many administrative concerns for the Danish and North Atlantic users. Universities or other institutions who makes use of WAYF, will likely benefit from using WAYF as login option.
Inform user regarding peer request - handle in web ui
Another option is simply to provide a notification in the web ui, so that there will be an indication of an action item until resolved. The mail sent to the user could then simply say that there is a new request from user x, or after a while a reminder on handling unresolved, pending requests.