InCommon metadata support

[Tom Scavo <>]

Hi Jeff,

On Tue, Jan 12, 2016 at 4:25 PM, Jeffrey Ramsay 
<>
 wrote:
>
> We're up and running on Shibboleth V3 and have had our JVM heap set well 
> above 1024 so, I think we're all set there.

Are you running the absolute latest version of V3? (The reason I ask
is that an important logging bug was fixed in V3.2.0.)

> The only uncertainty at the moment is what we need to do to be prepared for 
> the new aggregate.

Given what you said above, I think you will be able to consume the new
aggregate just fine. Do you have a test IdP? If so, you should point
it at the preview aggregate starting on Friday.

> Our production system is discoverable, don't have unneeded certificates in 
> our IdP metadata, contact information is up to date, a reasonable default 
> attribute release policy and we refresh InCommon metadata daily.

That's great!

> I'm not sure what / if anything else we need to do. I've been browsing the 
> site for weeks and have come across information regarding Refresh and 
> signing policies which differ from our current configuration.

Can you be more specific? What "refresh and signing policies" are you
referring to?

> Should we update our system or not -- this is the source of the confusion; 
> for me, it has not been a specific article -- I'm not sure where I should 
> stop reading. I just don't want our University to be affected because I was 
> unprepared.

Well, from what you've told me so far, you should be good to go.

> Lastly, concerning the Roadmap for eduGain - Phase two: will this be ready 
> Wed or Friday which is January 15th.

We will import eduGAIN metadata into the preview aggregate on Friday,
January 15.

Hope this helps,

Tom

> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Tom Scavo
> Sent: Tuesday, January 12, 2016 3:10 PM
> To: 
> 
> Subject: Re: [Metadata-Support] eduGAIN metatdata validator
>
> On Tue, Jan 12, 2016 at 2:50 PM, Jeffrey Ramsay 
> <>
>  wrote:
>>
>> This is very similar to what I had been following:
>>
>> https://spaces.internet2.edu/display/InCFederation/Registered+By+InCom
>> mon+Category
>
> Yes. In fact, the two pages are linked.
>
>> If clients like us do not need to worry about these attributes as they may 
>> only pertain to InCommon own IdP's, then why are we being asked to review 
>> information such as this and the validator.
>
> Can you tell me how you arrived at this conclusion? If there's 
> documentation that suggests this, I probably need to fix it.
>
>> Seems like busy work -- I'm trying to make sure we're compliant but the 
>> information provided is not very straight-forward.
>
> I'm not sure what page (or pages) you're looking at (besides the one 
> referenced above) but there are two particular pages of interest:
>
> 1) Upgrading to Shib IdP V3: https://spaces.internet2.edu/x/GYtHBQ
> 2) Getting Ready for eduGAIN: https://spaces.internet2.edu/x/VASDBQ
>
> If you have questions, let me know.
>
> Thanks,
>
> Tom
>
>> -----Original Message-----
>> From: 
>> 
>>  
>> [mailto:]
>>  On Behalf Of Tom
>> Scavo
>> Sent: Tuesday, January 12, 2016 2:33 PM
>> To: 
>> 
>> Subject: Re: [Metadata-Support] eduGAIN metatdata validator
>>
>> On Tue, Jan 12, 2016 at 2:24 PM, Jeffrey Ramsay 
>> <>
>>  wrote:
>>> Thank you! I thought so, but I couldn't find that information anywhere.
>>
>> Here's some info on the RegistrationInfo element:
>> https://spaces.internet2.edu/x/v4dHBQ
>>
>> Tom
>>
>