A client-server system for grid user and VO managemen

Schuller, Bernd

English

ZENODO

UVOS Web Registration Extension ManualUVOS WEB REGISTRATION EXTENSIONMANUALUNICORE TeamDocument Version: 1.5.1Component Version: 1.6.0Date: 21 01 2013This work is co-funded by the EC EMI project under the FP7 Collaborative Projects GrantAgreement Nr. INFSO-RI-261611.This work was co-funded by the EC Chemomentum project under the FP6 Grant Agreement Nr.IST-033437.UVOS Web Registration Extension ManualContents1 Introduction 12 Compatibility 13 Installation 13.1 Installation from RPM package (RedHat distributions) . . . . . . . . . . . . . 13.2 Installation from the DEB package (Debian distributions) . . . . . . . . . . . . 23.3 Installation from the archive . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Web browser path 35 Configuration 36 Developer howto 3UVOS Web Registration Extension Manual 1UNICORE VO Service (UVOS) is a client-server system, developed to be used as an additionaltool for large distributed systems, providing a solution for grid users management. Grid sys-tems, especially UNICORE grid middleware, are the mainspring of the UVOS system. UVOScan be used with different systems, however is designed primarily to support UNICORE gridmiddleware.For more information about UVOS visit http://uvos.chemomentum.org.1 IntroductionVO authentication web component provides a login user WWW interface for the UVOS system.It used to provide SAML HTTP POST or HTTP Redirect binding implementation: other webcomponents may redirect authentication requests to this component which authenticates thepresenter and returns a well-formated, signed document certifying this fact.The main features are:• support for interactive email+password authentication• support for authentication via web browser supplied certificate (i.e. client-authenticated TL-S/SSL). In this case user is authenticated as UVOS DN identity or UVOS X.509 identity(anyone which will succeed).• test mode: you can invoke the login servlet simply with HTTP GET. The authentication willbe performed but no SAML response will be generated.2 CompatibilityThis release is compatible with UVOS 1.4.0 and 1.4.1 (future versions might be supported too).3 InstallationUVOS web authentication extension is distributed either as a platform independent archive or asan installable, platform dependent package such as RPM. Depending on the installation sourceused, installation method and paths after installation are different.3.1 Installation from RPM package (RedHat distributions)The preferred way is to use Yum to install (and subsequently update) UVOS webauth.To perform the Yum installation, EMI Yum repository must be installed first. Refer to theEMI release documentation (available at the EMI website http://www.eu-emi.eu/releases ) forUVOS Web Registration Extension Manual 2detailed instructions. Typically installation of the EMI repository requires to download a singleRPM file and install it.After the EMI repository is configured, the following command installs UVOS webauth:$> yum install unicore-uvos-webauthThe installed extension will be placed in the directory /var/lib/unicore/uvos-server/-webapps/You have to restart UVOS server to complete the installation.3.2 Installation from the DEB package (Debian distributions)The preferred installation way is to use apt to install and subsequently update UVOS webauth.To perform the apt installation, EMI apt repository must be installed first. Refer to the EMI re-lease documentation (available at the EMI website http://www.eu-emi.eu/releases ) for detailedinstructions. Typically installation of the EMI repository requires to download a single DEBfile and install it.After the EMI repository is configured, the following command installs UVOS webauth:$> apt-get install unicore-uvos-webauthThe installed extension will be placed in the directory /var/lib/unicore/uvos-server/-webapps/You have to restart UVOS server to complete the installation.3.3 Installation from the archiveIf installing using a portable archive you have:1. Download the archive from the UNICORE download site and unpack it.2. In the unpacked archive you can find a file with a .war extension. Copy it to the webapps/directory of UVOS server. This directory is placed directly under installation root folderwhich was used when installing UVOS server from portable archive.You have to restart UVOS server to complete the installation.UVOS Web Registration Extension Manual 34 Web browser pathThe name of the war file is important as it is reflected in the URL by which web application isavailable. By default it is uvos-webauth-VERSION.war, where VERSION is e.g. "1.2". Youcan freely change the name of the war file. From now we will use label WAR_FILE_NAME torefer to actual base name of your war file.You should be able to reach the web UI indirectly (via redirect) at the address:<UVOS server base address>/WAR_FILE_NAMEor directly at:<UVOS server base address>/WAR_FILE_NAME/VOauthentication.doExample for the default server configuration and war named uvos-webauth-1.0.war:https://localhost:2443/uvos-webauth-1.05 ConfigurationIt is possible to change the default HTML page used for the logging the user. To do so:• create a new directory in UVOS server’s webapps folder with desired name and unpack wararchive into it.• remove the unpacked war file from the webapps directory.• modify CSS styles in template files located in WEB-INF/templates. Most of them arelocated in headerTop.ftl file.• restart the UVOS server.6 Developer howtoFor the high level understanding how the authentication works see documents:• SAML 2.0 core specification by OASIS - sec. 3.4 Authentication Request Protocol• SAML 2.0 bindings specification by OASIS - sec. 3.4 HTTP Redirect Binding• SAML 2.0 bindings specification by OASIS - sec. 3.5 HTTP POST BindingUVOS Web Registration Extension Manual 4To implement authentication in your servlet you have to:• Create and return a XHTML document to the user (which should be authenticated). Thedocument must contain POSTable form, with action equal to address of the web-auth servlet(contained in this package) installed at UVOS server. Check the Web Path Section 4 section tosee what URL you should use. Most often JavaScript is used to submit the form automaticallyto the web-auth servlet.• (and (hopefully) after while) Serve POST response with SAML response in it.You can match request and response by so called RelayState data which can be assigned to theinitial form and should be returned in the 2nd form.UVOS client library offers a class that implements all the logic to perform the above pattern.The class is pl.edu.icm.unicore.uvos.wsclient.samlapi.SAMLVOAuthnClientPO-ST See its javadocs. Also there is a mostly complete servlet example in this package howevernote that it won’t compile (that’s why it isn’t in sources) as it depends on uvos-client packagewhich is not available (and needed) for the uvos-webauthn package. This example is located inthe documentation directory and is called TestLoginServlet.java.

UVOS WEB REGISTRATION EXTENSION MANUAL

DataCite MDS

Uvos Web Registration Extension Manual

https://zenodo.org/record/6850/files/manual76.pdf

UVOS WEB REGISTRATION EXTENSION MANUAL

Abstract

Similar works

Full text

Available Versions

ZENODO

DataCite MDS