attribute release base on a cross-listed attribute in metadata

[Dave Perry]

Thanks Ian.
I dropped attribute-resolver, -filter and relying-party files in from the v2 config yesterday into the v3 system and it's erroring. I'll go through the log today and see if there are helpful hints to what it doesn't like.


Dave

_________________________________________________
Dave Perry
eLearning Technologist, Hull College Group

Room L34 - Queens Gardens Library
Wilberforce Drive, Queen's Gardens, Hull, HU1 3DG
Extension 2230 / Direct Dial 01482 381930

* Need a fast reply? Try elearning at hull-college.ac.uk *

Rate our service with the Library & eLearning Survey
For Students: http://library.hull-college.ac.uk/survey 
For Staff: http://library.hull-college.ac.uk/staffsurvey 


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Ian Young
Sent: 26 February 2015 10:03
To: Shib Users
Subject: Re: attribute release base on a cross-listed attribute in metadata


> On 26 Feb 2015, at 09:35, Dave Perry <Dave.Perry at hull-college.ac.uk> wrote:
> 
> I think on our v2.3.8 IdP that targetedID is used, but I'm setting up a v3 one currently to supercede it.
> Will users not lose existing personalisation if we use the new NameID approach?

The simplest approach is to reuse your v2 attribute release configuration under v3. That way, the same attributes will be released as before and compatibility will be preserved. You don't have to start from scratch; moving to v3 and your attribute policies can be entirely separate discussions.

    -- Ian





**********************************************************************
This message is sent in confidence for the addressee
only. It may  contain confidential or sensitive
information.  The contents are not to be disclosed
to anyone other than the addressee.  Unauthorised
recipients are requested to preserve this
confidentiality and to advise us of any errors in
transmission.  Any views expressed in this message
are solely the views of the individual and do not
represent the views of the College.  Nothing in this
message should be construed as creating a contract.

Hull College owns the email infrastructure, including the contents.

Hull College is committed to sustainability, please reflect before printing this email.
**********************************************************************

TEXT