...wip...

Description

WaTTS activity is to provide a token translation functionality. It allows service. Its purposeful design is to facilitate usage and integration of legacy services, such as SSH enabled services and services that consume "token-based" credentials with federated identities, Examples are services requiring SSH keys or services requiring the use of X.509 certificates, with federated identities.  For For this, WaTTS accepts is accessed using federated identities (via OpenID Connect) and uses a plugin scheme to generate necessary credentials for your service. This the desired service. For source of federated identities that do not use OIDC, it is recommend to integrate WaTTS with one of the existing SP-IdP-Proxy solutions. This allows users to access services that support only non-federated authentication mechanisms , using their federated identities. Relying Services can subscribe to the credential translation service of the Life Science AAI provided by WaTTS, allowing the users to obtain X.509 certificates based on their Life Science IDs. Using WaTTS, and after obtaining an initial proxy certificate from RCauth. WaTTS will provide eu online CA, WaTTS stores the proxy certificate in a trusted credential store connected , and subsequently provides the proxy (or more accurately, proxy of the proxy) to the RCauth.eu online CA and through SSH. Additional plugins for common services already exist to support additional legacy user. User can also upload its SSH public key, with which the user can obtain the proxy certificate via command line. Additional plugins are also present to support other services.

WaTTS is developed by KIT with funding from INDIGO, and for LS AAI pilot is operated as a service through from EUDAT and KIT.

User Guide

At the following link is available a complete guide related to WaTTS.

...