InCommon metadata support

[Nick Roy <>]

Hi Oscar,

I’ve replied to your request about this via , separately.

As far as attributes you’ll need to configure, general information may be found here: https://www.incommon.org/federation/attributes.html

The short version of this is that you’ll want to configure:
eduPersonPrincipalName (which should be unique for each user in your system, and preferably not reassigned)
eduPersonAffiliation
eduPersonScopedAffiliation
mail
givenName
sn
displayName

Some applications may need other attributes, for example campus ERP applications that you federate with may want a university ID number, student records number, etc. You will typically know that you need to configure these when you work through configuration with one of these types of services.

Best,

Nick

On 16 Apr 2019, at 14:23, Oscar Ruiz wrote:

Hello,

Our institution is in the process of registering as an InCommon participant. We have access to the Federation Manager Portal and would like to register our shibboleth IdP and were wondering how to go about doing that if we already had a metadata xml file, it seems like the interface to add a new IdP generates a new file or do I need to add the values in my file to the input fields requested? Or do we need to register our IdP as a service in InCommon?

Also, is there a page on your wiki that goes over which attributes need to be configured for release from the IdP? I’ve gone over most of the pages on this section https://spaces.at.internet2.edu/display/InCFederation/Federation+Technical+Guide#FederationTechnicalGuide-StartingwithInCommon and the page that talks about Identity Attributes Overview (https://spaces.at.internet2.edu/display/InCFederation/Supported+Attribute+Summary), it looks like the information there is deprecated.

Thanks for your help,

Oscar

Attachment: signature.asc
Description: OpenPGP digital signature