Skip to content

Latest commit

 

History

History
75 lines (41 loc) · 1.91 KB

README.md

File metadata and controls

75 lines (41 loc) · 1.91 KB
Raw

Dataporten deployment

This is a script for deploying dataporten authentication for galaxy via apache httpd / openidc.

Usage:

./deploy.sh

Prerequisites

Dataporten application

You need to have the dataporten openid information ready. For development instances, you can do this yourself. On https://dashboard.dataporten.no/, you will need to register an application. After registering, you will find the Client ID and Secret ID under OAuth credentials. For production, this should be ordered as UiO.

The important fields are:

Redirect URI

This is a url only for contact between the httpd server and dataporten. The domain name has to be the exactly same domain name that are used for the service.

https://[domain name]/callback

for example:

https://lifeportal.uio.no/callback

Auth providers

Select which providers the portal will use.

Permissions

Should be set to:

  • E-post
  • OpenID Connect
  • Profilinfo
  • Bruker-ID

Administrators

For portals maintained by FT, FT should be added as an administrator.

For services in production, Extended info should be filled out

This is not necessary for development instances.

Galaxy-register

The database information from the galaxy-register service and the service name (for example lifeportal)

Maintenance page

A page for redirecting under maintenance should be set. For Lifeportal, this is the operational log: https://www.uio.no/english/services/it/research/hpc/lifeportal/log/

What it does

Installs mod_auth_openidc

The script downloads and installs the rpm packages for mod_auth_openidc.

Updates httpd.conf and ssl.conf

Usage

Maintenance stop

To accept login for only certain users under a maintenance stop, set maintenance_stop to yes in /etc/galaxy_email.cfg and restart httpd.

To be implemented:

  • Creation of SSL keys and correct placement of these