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  February 2008

JISC-SHIBBOLETH February 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Seems you can't take your settings to the fed

From:

Fiona Culloch <[log in to unmask]>

Reply-To:

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

Date:

Mon, 25 Feb 2008 23:13:08 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (55 lines)

> thanks Fiona. Eduserve were going to send me details of how they generate
> a persistent ID from EPTI, which they then give to the resources behind
> the gateway. If the value is different for each resource 

Observing the behaviour using the Shibboleth to Athens gateway from
our IdP, the same Athens Persistent User ID (PUID) is presented to
different Athens resources for the same gateway user, which is what
I'd expect.

> then there's a
> chance we can "migrate" the settings from Athens to the fed by
> implementing those rules against our EPTI for those providers who have
> settings "locked-in".

I don't see how this could work just by changing things at your end;
you'd have to clarify that after you get your information from
Eduserv.  But consider this first...

> It's still at the hand waving stage but AFAIK the resources, such as
> Digimap, key settings against the munged value of EPTI they get from the
> gateway. 

The PUID is not so much a munged ePTI as an arbitrary value in
a database at Athens that is looked up based on your ePTI values.

For an Athens login, which is what the Shibboleth to Athens gateway
does, the PUID is what the resource sees.  The ePTI is lost (not
passed along) but even if it were, in the general case the Athens
resource is going to be existing code that wouldn't understand or be
interested in it anyway.

> Theorising for a moment, that would suggest that if we gave
> Digimap the same value of EPTI when accesing it via the fed, then the
> settings will still be accessible.

For a direct federated login, the Digimap SP sees the value of ePTI
that your IdP releases to it.  Since it is a different SP from the
gateway SP, it should see a different targeted id value even if the
underlying ePTI were visible in the Athens case, which it isn't
(without modifying the gateway).

> All we need are the munging rules,
> which we can then implement in our IdP. It might work, it might be pie in
> the sky(e) but I'm waiting to get the details of the munging rules.
>
> Hopefully it'll all come out in the wash.

I'm not hopeful of this, for the reasons set out above.  Something
along those lines might conceivably be made to (sort of) work
_iff_ you were able to modify the IdP code, the gateway code and
the code at all DSP & SPs of interest to fit, which doesn't seem
likely.

Fiona.

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