1 / 13

Secure Access to Shibboleth Protected Clusters

Secure Access to Shibboleth Protected Clusters. Jan Meizner (1), Maciej Malawski (1,2), Marian Bubak (1,2) (1) ACC Cyfronet AGH , ul. Nawojki 11, 30-950 Kraków, Poland (2) Institute of Computer Science AGH , Mickiewicza 30, 30-059 Kraków, Poland. KUKDM 2010 Zakopane, 18.03.2010.

oona
Télécharger la présentation

Secure Access to Shibboleth Protected Clusters

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Secure Access to Shibboleth Protected Clusters Jan Meizner (1), Maciej Malawski (1,2), Marian Bubak (1,2) (1) ACC Cyfronet AGH, ul. Nawojki 11, 30-950 Kraków, Poland (2) Institute of Computer Science AGH , Mickiewicza 30, 30-059 Kraków, Poland KUKDM 2010 Zakopane, 18.03.2010

  2. Outline Introduction Problem definition Scientific objectives Related work Why Shibboleth and its description Description of the proposed solution Video demo with a short introduction PAM_SHIB configuration Conclusions and future work

  3. Introduction The main reason for the work is to provide manageable access to clusters by using the Shibboleth architecture Scientific objectives: Providing swift access to clusters for scientists using standard command-line (console) tools Laying a foundation for Shibboleth-secured web-based applications with seamless access to computing clusters Enable access to clusters for other projects/organizations, if needed, by using Shibboleth federation mechanisms

  4. Related work Simple passwd file-based access (pam_unix) Standard solution in Linux Common in small systems (single machines) Completely not scalable Andrew G. Morgan, Linux-PAM, 2010, http://www.kernel.org/pub/linux/libs/pam/ LDAP-based authentication (pam, ldap or similar solution) Allows centralized management of credentials No Single Sign On supported (out of the box), no federations PADL Software Pty Ltd, 2010, http://www.padl.com/OSS/pam_ldap.html Raw key pair-based authentication (e.g. OpenSSH publickey method) Equivalent to SSO if unencrypted keys are used (not secure) Requires generation of keys and distribution to all nodes and clients OpenBSD Project, OpenSSH, 2010,http://www.openssh.com/ Software solution using X.509 authentication (e.g. GSI-OpenSSH) Provides Single Sign-On Requires application for a certificate and its distribution to client machines University of Illinois, GSI-Enabled OpenSSH, 2010. http://grid.ncsa.illinois.edu/ssh/ Hardware-based security solutions (e.g. smartcards) More secure and easy then “software” certificates More complicated and costly issuance procedures

  5. WhyShibboleth? A well known solution, widely used by scientific and educational institutions Provides Single Sign-On mechanisms Federated solution - access can be granted to users from new institutions with no need to recreate accounts No need to request certificates or generate and distribute keys More secure then using unencrypted keys, more manageable then using encrypted ones Well suited for protection of web applications

  6. The Shibboleth • HO1 & HO1 – Home Organizations • IdP – Identity Provider – composed of: • SSO – Single Sign On • AA – Attribute Authority • SP – Service Provider • SAML - Security Assertion Markup Language HO1 HO2 IdP SP SAML The Shibboleth framework is used to provide a federated Single Sign-On mechanism. It enables various institutions to collaborate by sharing access to the resources among their users without the need to duplicate user databases (create and manage multiple accounts).

  7. Description of the solution The server side is composed of: Shibboleth framework deployed on at least one server for each entity providing LDAP databases for their users The pam_shib module, developed by us. This module needs to be deployed on each node to which ssh access should be provided Standard OpenSSH server (or other server with PAM support) (Optional) Custom Shibboleth-aware software on any node For the client side we provide: Custom Shibboleth IdP Client tool Patched version of the standard OpenSSH client that can automatically use the stored handle (however, an unmodified client may also be used)

  8. Description of the solution Shibboleth Identity Provider Client tools Handle response Handle request Single sign on Attribute authority Portal application Standalone client Credentials Run Attributes Return Main LDAP Local replica Shibbolized services Nodes with pam_shib installed Replication Attributes response Attributes request Credential source Resources

  9. What’s on the video demo? • During the demo we’re going to show single authentication to the Shibboleth IdP, followed by a series of ssh connections (using auto-delegated credentials): • From A to B • From B to C • From C to A • Again from A to B • Subsequently, we’re going to show that password authentication still worksonce the Shibboleth handle has been removed Network with a Shibboleth Framework Node A Node B Node C The video has been recorded using 3 computer nodes (A, B and C) connected with LAN. Node A is a laptop acting as the User Interface. On this node a Shibboleth IdP client is installed. OpenSSH servers and shib_pam modulesare installed on all nodes, as well as patched OpenSSH clients. Shibboleth is deployed on a separate (remote) network.

  10. The video demo… PAM_SHIB DEMO

  11. PAM_SHIB configuration To enable access to the node, the administrator needs to: Install required libraries (opensaml,curl and their dependencies) Install the module and the configuration file into appropriate locations (e.g. /lib/security and /etc) Add the module to service's (e.g. ssh) pam configuration following the basic authentication module (e.g. after pam_unix) Ensure that both basic (pam_unix) as well as pam_shib modules are set to be sufficient to grant access to the resources and that pam_shib has its conf parameter set to the appropriate configuration file

  12. Conclusions and further work The goals have been achieved – creation of the pam_shib modules broadensthe pool of software that can be accessed with Shibboleth credentials. In addition to Shibboleth-enabled software that could be accessed before, various native software packages installed on clusters can now be offered to users Work is in progress on the following issues: Making the module more versatile and user friendly by providing more manageable configuration mechanisms Integrating the solution with GridSpace 2

  13. References J. Meizner, M. Malawski, E. Ciepiela, M. Kasztelnik, D. Harężlak, P. Nowakowski, D. Król, T. Gubała, W. Funika, M. Bubak, T. Mikołajczyk, P. Plaszczak, K. Wilk, and M. Assel. ViroLab Security and Virtual Organization Infrastructure. In Young Dou, Ralf Gruber, and Josef Joller, editors, Advanced Parallel Processing Technologies 8th International Symposium, APPT 2009, Rapperswil, Switzerland, August 24-25, 2009 Proceedings, volume 5737 of Lecture Notes in Computer Science, pages 230–245. Springer, 2009 GridSpace webpage, http://gs.cyfronet.pl/ PL-Grid Project, http://www.plgrid.pl/en

More Related