Skip to content

Latest commit

 

History

History
89 lines (72 loc) · 3.72 KB

motley-cue.md

File metadata and controls

89 lines (72 loc) · 3.72 KB

Mapper (motley-cue)

Depending on your distribution, install with either:

  • apt-get install motley-cue
  • yum install motley-cue
  • zypper install motley-cue

This will pull a couple of dependencies, most notably nginx (for which epel-release is required on centos7). You SHOULD get a host-certificate for your server and enable https in nginx. This is not part of this documentation.

Host Configuration

  • Open your firewall on port 8080

  • OR install a host certificate with nginx and open your firewall on port 443

  • Notes on selinux (for centos7 and centos8):

    • We tested pam-ssh-oidc and motley-cue in permissive mode only.
    • We succeeded in running in enforced mode, by using these commands:
      semodule -i /usr/share/motley-cue/selinux/motley-cue-gunicorn.pp
      semodule -i /usr/share/motley-cue/selinux/motley-cue-sshd.pp
      semodule -i /usr/share/motley-cue/selinux/motley-cue-nginx.pp
      setsebool -P nis_enabled 1
      
    • Feedback is appreciated

motley-cue configuration

Configuration of motley-cue takes place in /etc/motley-cue:

  • motley_cue.conf: Authorisation configuration: Allows definition of the Virtual Organisation (or groups) that are allowed to use the service.
  • feudal_adapter.conf: Account creation configuration: Allows among others to configure the account creation, including the levels of assurance.

Additional configuration:

  • /etc/nginx/sites-enabled/nginx.motley_cue: NGINX configuration: web-server specific configurations, such as ports or host certificates.

Assurance Configuration

The config file is self documenting. Even more information may be found here. By default from the motley-cue package, the following defaults are set:

  • Username creation:
    • Try to respect incoming preferred_username
    • If not iterate over combinations of first and last name
  • Assurance:
require = profile/espresso |
    IAP/medium & ID/eppn-unique-no-reassign |
    IAP/low & ID/eppn-unique-no-reassign |
    https://aai.egi.eu/LoA#Substantial |
    profile/cappuccino

Authorisation Configuration

You can support multiple OPs and configure authorisation for each OP separately. There are three options to authorise users:

  • authorise all: allow all users from a trusted OP
  • individual: authorise single users via their unique identifier given by sub + iss
  • VO-based: authorise users that are members of a specific VO (or a set of VOs)

The VO definitions allowed include:

The default configuration contains several examples (commented out), but you'll need to modify /etc/motley_cue/motley_cue.conf to enable any authorisation.

You can find out your own groups with:

mccli info --oidc <oidc-agent account name>