andreaceccanti

Keybase proof

I hereby claim:

• I am andreaceccanti on github.
• I am andreaceccanti (https://keybase.io/andreaceccanti) on keybase.
• I have a public key ASAjMuawZd0I9FLqw0FuWSmyFPLMsBrooAodO7p7kT_PJgo

To claim this, I am signing this object:

andreaceccanti

#!/bin/bash
set -e

exit_msg() {
  echo "Giving up as requested by user..."
  exit 1
}

if [[ -z "${IAM_DEVICE_CODE_CLIENT_ID}" ]]; then
  echo "Please set the IAM_DEVICE_CODE_CLIENT_ID env variable"

andreaceccanti

oidc:
  providers:
  - name: google
    issuer: https://accounts.google.com
    client:
      clientId: ${IAM_GOOGLE_CLIENT_ID}
      clientSecret: ${IAM_GOOGLE_CLIENT_SECRET}
      redirectUris: ${iam.baseUrl}/openid_connect_login
      scope: openid,profile,email,address,phone
    loginButton:

andreaceccanti

RUCIO/FTS TPC scenario (service identity, capability-based authz)

In this scenario, RUCIO and FTS managed transfers using their service identity.

The chain of services is

RUCIO -> FTS -> SE1, SE2

RUCIO wants to trigger transfer of file /cms/example from SE1 to SE2.

andreaceccanti

VOMS REST API documentation

VOMS implements a REST API that can be used to get a VOMS attribute certificate.

API endpoint

https://<voms.host>:<voms.port>/generate-ac

Authentication requirements