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

Help for MOONSHOT-COMMUNITY Archives


MOONSHOT-COMMUNITY Archives

MOONSHOT-COMMUNITY Archives


MOONSHOT-COMMUNITY@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

MOONSHOT-COMMUNITY Home

MOONSHOT-COMMUNITY Home

MOONSHOT-COMMUNITY  February 2013

MOONSHOT-COMMUNITY February 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: It's Trust Routers all the way down: obtaining RADSEC credentials for TRs and TIDRs

From:

Sam Hartman <[log in to unmask]>

Reply-To:

Sam Hartman <[log in to unmask]>

Date:

Thu, 14 Feb 2013 18:10:28 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

>>>>> "Jim" == Jim Schaad <[log in to unmask]> writes:

    Jim> QUESTIONS:

    Jim> 1.  To what degree do the trust router components tightly
    Jim> coupled to the AAA proxy on the Relying Party and the IdP need
    Jim> to get the Trust Route flooding information?  If the trust
    Jim> router next to the RP needs to talk to different trust
    Jim> infrastructures based on COI, then it needs to know what COIs
    Jim> are in each Trust Router.  In a private mail to Sam & Margaret,
    Jim> I suggested a reason why the trust router next to the IdP might
    Jim> need to get the same information.


In the current architecture, trust routers basically need the full
routing table.

However, a temporary identity client (coupled with the RP proxy) and a
temporary identity server  (coupled with the IDP) never need the full
routing table.
a TIC only talks to one trust router or possibly to multiple ones for
redundancy.
TICs never make routing policy decisions.
If you need routing policy decisions, introduce a real trust router.


    Jim> 2.  To what degree does a Trust Router in the system have a
    Jim> special relationship with the IdP(s) that authenticate the
    Jim> Trust Route infrastructure.  It is my opinion that there will
    Jim> be one (or more) TRs that are "privileged" in that they will
    Jim> have a pre-configured existing relationship with the trust
    Jim> router IDP entity (TR-IDP).  If there are multiple TRs in a
    Jim> web, not all of the TRs may have this "privileged" relationship
    Jim> and if there are multiple "clones" of TR-IDP or multiple IDPs
    Jim> that can allow access to the TR COI then 1) every IDP has some
    Jim> TR which is in a privileged relationship and 2) a single TR may
    Jim> have a privileged relationship with zero or more IDPs.

Well, a TR doesn't directly have a privileged relationship with the
TR-IDP, or what I'm calling an APC realm.
However, the APC realm does run some TIS.
Generally, a TIS has a small ACL for who can talk to it. Generally that
ACL includes only a small number of trust routers who are directly
connected to the TIS.

So, there are privileged trust routers in the sense that they are
authorized to create temporary identities in the APC realm.
I'd expect a small number of these per APC realm.

Note that there can be more than one APC realm per APC. I haven't
explained that yet, although Josh and I did a walk through of how that
works after my message Tuesday.
I'll write that up soon.

Note there's another form of privilege: each trust router has a
privileged relationship with exactly one RP realm--the realm in which it
accepts authentications.

That is, there's one realm worth of RADSEC servers that a trust router
can talk to.
That realm is responsible for connecting the trust router's acceptor
components to the rest of the universe.

    Jim> 3.  What information does the RP AAA proxy need for indexing of
    Jim> the temp ids for a given IdP's AAA proxy server?  At a minimum
    Jim> I think this is the COI, the APC, the IdP Server Realm..
    Jim> Additionally one would have the keys, the temp id and the
    Jim> lifetime of the temp id.


For indexing? There's a key identifier that's part of TLS PSK. I think
the IDP realm and TLS PSK ID should be sufficient to look up a key on an
RP proxy.
However, the set of communities (both APCs and COIs) that key is valid
for is important to track.
Lifetime as well once that becomes finite.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2022
December 2021
October 2021
September 2021
August 2021
June 2021
April 2021
February 2021
January 2021
December 2020
November 2020
October 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
January 2020
November 2019
October 2019
September 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
June 2018
April 2018
November 2017
October 2017
September 2017
August 2017
July 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 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
July 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
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010


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