Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Using e-mail as SubjectID & merging users

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Using e-mail as SubjectID & merging users

Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: Francesco Cepparo <>
  • Cc: "" <>
  • Subject: RE: [grouper-users] Using e-mail as SubjectID & merging users
  • Date: Mon, 28 Mar 2016 06:58:50 +0000
  • Accept-language: en-US
  • Authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23

Im not sure how to do a JDBC source with a multivalued attribute, does someone have an example of that?





From: Francesco Cepparo [mailto:]
Sent: Saturday, March 26, 2016 7:46 AM
To: Hyzer, Chris <>
Subject: Re: [grouper-users] Using e-mail as SubjectID & merging users


Well, I guess we could use the opaque ID if the e-mail wouldn't work no matter what. What puzzles me the most at the moment, is that importing users using the opaque ID works, but it does not when using e-mails. Also, by using the opaque ID, we would have to merge the Subjects by hand.


About issue #2, if we do a distinct query, many of the entries in the database would be ignored, and we don't want that. We would like the entries with duplicate IDs to be inserted into a single Grouper Subject.

For example, if we have the following table:


id | test | email

1 | ABC |

2 | DEF |

3 | GHI |


we would like to have two Grouper Subjects, one identified by , and the other by , where the email1 user would have both the "ABC" and "DEF" values for the attribute "test" in Grouper.

I now understand that by using the ID we would have to do the merging by hand and create a registry, and maybe also create another unique ID if we have multiple sources. Instead, by using the email, we are hoping that the merging occurs automatically. What would Grouper do when it encounters the duplicate IDs (assuming we succeed in importing users by email)?




2016-03-25 22:53 GMT+01:00 Hyzer, Chris <>:

If you have something else like an opaque id, then use that.  If not, and you have no registry for users to assign a uuid or something, then I guess email is all you have J.  In your database you don’t have a userId col or something?  The primary key is email address?  Is there a facility for users to change their email address in the system?


Not sure I understand issue #2.  Can you have a distinct query in your subject API config or something?


From: Francesco Cepparo [mailto:]
Sent: Friday, March 25, 2016 12:23 PM
To: Hyzer, Chris <>
Subject: Re: [grouper-users] Using e-mail as SubjectID & merging users


Thanks, I will try debugging as soon as I can. About the other issues:

1) If we use a custom, opaque identifier, then how do you usually implement this? I mean, how would the application know how to retrieve the correct user in Grouper?

2) What I meant by merging users, was that the email is not unique in the database, but entries with the same email should belong to the same Grouper Subject, so we want the Grouper Loader to merge those entries into a single Subject. Does it do this automatically if we use the e-mail as the SubjectID?


Thank you.


2016-03-25 16:45 GMT+01:00 Hyzer, Chris <>:

I hesitate to respond to this since email as identifier is a hot button issue J


There is Internet2 SubjectId and SubjectIdentifier.


The SubjectId is something that shouldn’t change, it should be opaque.  But if you must have it be something that can change, up to you J

A SubjectIdentifier is something that can uniquely lookup a user.  I haven’t heard of email being used for this, but if each email address uniquely identifies a user, you could certainly do it that way J


If you have multiple subjects with different subjectIds and you want to merge them together, you can do a memberChangeSubject

You can have multiple subjects with different identifiers (e.g. emails) and that is fine.


The authentication can use email as id, that doesn’t mean it has the be the subjectId in grouper, it can be an identifier


If it ran successfully and didn’t populate the group, then check the logs.  Maybe add debug to the loader in = DEBUG





From: [mailto:] On Behalf Of Francesco Cepparo
Sent: Thursday, March 24, 2016 8:10 AM
Subject: [grouper-users] Using e-mail as SubjectID & merging users



we're trying to configure the Grouper Loader to import users from a database. Each user is identified by an e-mail, but, in the database, there might be multiple entries with the same e-mail, and we would like to merge those entries into a single Subject in Grouper. Is this possible?


Also, is it possible to use e-mails as SubjectIDs? Our authentication system uses e-mails as IDs, and we would like to configure Grouper to use e-mails as well, to be able to reference users in an unified manner. However, when trying to load the users using the e-mail as the ID, the loader says that it ran succesfully, but that it inserted 0 memberships out of the 401 total memberships. (It doesn't work even if there are no duplicate e-mail entries)


Thank you.



Archive powered by MHonArc 2.6.16.

Top of Page