JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH Archives

JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH  April 2007

JISC-SHIBBOLETH April 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Athens resouces on the UK federation

From:

Ian Young <[log in to unmask]>

Reply-To:

Discussion list for Shibboleth developments <[log in to unmask]>

Date:

Tue, 17 Apr 2007 11:49:48 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (64 lines)

Andy Swiffin wrote:

> The Identity Provider Deployment document from the "Federation" site
> says:
> 
> "eduPersonTargetedID.  this attribute provides a consistent, opaque
> pseudonym for the user that is different for each service provider"
> 
> How does that work?    I would imagine we hash the userID and store
> that away in a directory attribute which is made available to the IdP
> but that is just one value, if it is different when delivered to each SP
> who makes it different?

The example implementation of eduPersonTargetedID that is provided with
current versions of the Shibboleth IdP operates by hashing together:

	the user ID

	the SP's entity name

	a secret

The advantage of this approach is that there is no need to store
additional information.  It has numerous disadvantages, though, and as a
result many sites will end up doing something that involves storing data
somewhere.

> Responding to what Karen said - we are one of the majority of
> institutions that do re-use user IDs, so could not sign up to the
> non-reassigned clause.

Not true.  The requirement not to reassign the same ePTI to different
people can be met by any technical means you choose.  If you reassign
user IDs, you clearly can't rely on the simple technical means provided
by the example plug-in provided in the IdP distribution; you'll have to
do something else.  So the reuse of user IDs does not rule out being
able to assert user accountability for federation purposes, you just
have to work harder.

>  But, could we not attach, for example, a year
> indicator to the userID thus making it unique and then hash that and
> store it in the eduPersonTargetedID attribute?  So for example should I
> leave Dundee and another alswiffin turn up a couple of years later, even
> though their local login ID would be the same, i.e. alswiffin,  for the
> purposes of eduPersonTargetedID I would have been a hashed alswiffin2007
> and they would be a hashed alswiffin2009 hence unique.   

If you have an attribute store that includes both a local principal name
and a year-qualified principal name then you can use the year-qualified
version to feed into your eduPersonTargetedID calculations and you've
met the non-reassignment criteria for ePTI.

It is in fact possible to configure the Shibboleth IdP to use the
example ePTI plug-in and have it take the "user ID" component from any
subject attribute, so this wouldn't really be much work (other than
populating the qualified principal name attribute).

You might still want to look at actually storing ePTI values for each
principal/SP combination to allow for things like disassociating a user
if they think one of the SPs has compromised their privacy, but that's a
separate question.

	-- Ian

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

November 2023
February 2023
January 2023
November 2022
October 2022
September 2022
June 2022
January 2022
November 2021
October 2021
September 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
April 2015
March 2015
February 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager