Grouper Users - Open Discussion List

[Chris Hyzer <>]

This was designed in the grouper external users module...

Basically you need to adjust your grouper.properties, and then generate the 
DDL for the external users view...


#####################################
## External subjects
#####################################


# note, this must be only alphanumeric lower case or underscore
# (valid db column name, subject attribute name)
externalSubjects.attributes.firstName.systemName = firstName
externalSubjects.attributes.firstName.required = true
# comment on column in DB (no special characters allowed)
externalSubjects.attributes.firstName.comment = First name


# note, this must be only alphanumeric lower case or underscore
# (valid db column name, subject attribute name)
externalSubjects.attributes.lastName.systemName = lastName
externalSubjects.attributes.lastName.required = true
# comment on column in DB (no special characters allowed)
externalSubjects.attributes.lastName.comment = Last name



Look at the rest of the configs to see if you need to adjust, e.g.

externalSubjects.desc.el

externalSubjects.searchStringFields

etc

Note: I didn't really plan on "name" not being there, and it seems weird that 
the user would fill in their name, first name, and last name.  

We could support something like this pretty easily I believe:

externalSubjects.name.el = 
${grouperUtil.appendIfNotBlankString(externalSubject.attribute['firstName'], 
' - ', externalSubject.attribute['lastName'])}
# true if the description should be managed via EL (config above)
externalSubjects.name.manual = false

You can do a gsh -registry -deep, do you not run the script, and look for the 
drop and create of view GROUPER_EXT_SUBJ_V, then make sure they make sense 
and run them...

Thanks,
Chris


-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Peter DiCamillo
Sent: Thursday, March 14, 2013 3:45 PM
To: 

Subject: [grouper-users] Name and other attributes for external subjects

We're running the current version of Grouper, and working on supporting 
Grouper's external subjects in our various applications. We've run into 
a problem with the names for external subjects. During the invitation 
process, the person enters their name in a single field. However LDAP 
(RFC 4519), and other applications such as Canvas require a first name 
and last name for people. While we can easily construct a full name from 
the first and last name, it's not possible do the reverse reliably. So 
we'd like to have Grouper prompt for and save first and last names for 
external subjects. While it's not as essential, we've also realized that 
it would be very useful if external subjects had an attribute 
identifying the person who invited them. Does Grouper provide 
customization mechanisms for these changes, or if not, could they be 
included in Grouper at some point?

Peter