perfsonar-dev - Re: [pS-dev] AA next steps and tests
Subject: perfsonar development work
List archive
- From: Cándido Rodríguez Montes <>
- To: Nicolas Simar <>
- Cc: 'Stijn Melis' <>, "" <>
- Subject: Re: [pS-dev] AA next steps and tests
- Date: Wed, 5 Sep 2007 13:59:11 +0200
Hi Nicolas, El 05/09/2007, a las 9:55, Nicolas Simar escribió:
We have the authn library for this case and it's integrated with the SASL-CA server and the eduGAIN metadata service (MDS). The library asks MDS for the available federations in eduGAIN and also it can get a valid X.509 certificate from a SASL CA server. But, before it can be used, the following problems have to be resolved: + Contact information of the SASL CA server of a federation have to be included in the MDS. This has been requested to JRA5 guys because it hasn't beed specified how to include the information of this kind of software in the MDS. + Certificates issued by SASL CA have a bug and I'm waiting a new release from Derek Morr. Until this problem would be resolved, I'm writting the documentation and tutorials in the wiki. I'll advise when it'd be available!
Is there any AC for the SSH Telnet MP?
Is there any WE for the SSH Telnet MP? Anyway, as implementing the authentication process is so easy (I hope :) ) I think we can choose another pS web-service contacted by a AC or a WE so we can test that case.
A full connection with the GIdP will be done when: - GIdP would be available in the MDS (I'll send an email to Maurizio for this). - SASL CA server would be deployed for the GIdP (Waiting for the new version of SASL-CA)
Ok
Also, there is another task: moving all authn classes to the new svn structure. I hope it will be done by Friday.
Well, after the Sitjn's work, we can think that the integration of the authn in a perfSONAR web-service (pSR) is easy, so, I think we should start with clients. Why? Because if clients implement the authn process, it doesn't matter if the pSR have implemented too. But, in the other case, if pSRs implement the authn process and clients not, pSRs will send them an authentication error. So, for the pSR that we want to add the authn process, which clients connect them? only perfSONAR UI (which is in the UbC case)? Anyway, I think we can proceed ahead. Of course, we can find some bugs, but it will be fixed as soon as possible.
Also, if there are perl clients which connect them, we should know it, so we can help their developers for integrating them in the authn process.
Well, all X.509 certificates and SAML assertions include the component ID (cID) of the client/user. It has the information about the name of its federation and its unique ID. We can filter the authorization by any cID, cIDs from an specific federation or by specific federation and the ID of the client/user. So, we can define a basic "policy" for the authorization right now.
I think so :) Regards
-- Cándido Rodríguez Montes E-mail: Red.ES/RedIRIS Tel:+34 955 05 66 13 Edificio CICA Avenida Reina Mercedes, s/n 41012 Sevilla SPAIN |
- AA next steps and tests, Nicolas Simar, 09/05/2007
- Re: [pS-dev] AA next steps and tests, Cándido Rodríguez Montes, 09/05/2007
- Re: [pS-dev] AA next steps and tests, Jochen Reinwand, 09/05/2007
- Re: [pS-dev] AA next steps and tests, Nicolas Simar, 09/05/2007
- Re: [pS-dev] AA next steps and tests, Stijn Melis, 09/11/2007
- Re: [pS-dev] AA next steps and tests, Cándido Rodríguez Montes, 09/05/2007
Archive powered by MHonArc 2.6.16.