2012/3/1 Nikolai Vazov <n.a.vazov@usit.uio.no>

Hi,

we work at the University of Oslo, USIT, The Research Computing Service group (Norway). We are preparing a bioinformatics portal using Galaxy and one of the requirements for the University of Oslo production is to implement an authentication called FEIDE. Feide is local (for Norway) IDp service based on saml2 which is yet different from OpenID. It supposes the existence of metadata files on the sp server side containing blocks with, e.g. (for idp)

'SingleSignOnService' => 'https://idp.feide.no/simplesaml/saml2/idp/SSOService.php',
'SingleLogoutService' => 'https://idp.feide.no/simplesaml/saml2/idp/SingleLogoutServiceiFrame.php',
'SingleLogoutServiceResponse' => 'https://idp.feide.no/simplesaml/saml2/idp/SingleLogoutServiceiFrameResponse.php',
'certFingerprint' => 'cde69e332fa7dd0eaa99ee0ddf06916e8942ac53',
'hint.cidr' => '158.38.0.0/16'

These blocks are read during the authentication process.

Galaxy seems to be only supporting OpenID and new idp-s are added simply by adding a new url to OPENID_PROVIDER variable.

Is there a solution if we have to communicate metadata between idp and sp?

And ... is your egg "python_openid-2.2.5-py2.6.egg" using pysaml? Can it be rescrambled such that it can read some pysaml metadata files.

Thank you in advance

Nikolay Vazov

--
Nikolay Vazov, PhD
Research Computing Centre - http://hpc.uio.no
USIT, University of Oslo

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

http://lists.bx.psu.edu/