Skip to content

Test Environment for Artemis with SAML2 / Shibboleth

License

Notifications You must be signed in to change notification settings

kit-sdq/Artemis-SAML2-Test-Docker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Artemis Configuration SAML

Test environment for the SAML2/Shibboleth Feature in Artemis.

Instead of configuring the whole containers you can obtain a preconfigured data archive from the releases page

Some interesting effects by OS

Linux Users

You may have to ..

  • run all commands as root esp. tar xzf data.tgz to ensure that permissions are correct

Instructions for local testing

  1. Clone the repository
  2. Run docker compose up -d and wait for the initial startup of the backend (config files will be copied). After that, stop the backend: docker-compose stop artemis
  3. Configure Artemis with Jenkins as usual. Setup SAML using the configuration file as follows:

The application-saml2.yml must look like that:

saml2:
    username-pattern: 'saml2-{first_name}_{last_name}'
    first-name-pattern: '{first_name}'
    last-name-pattern: '{last_name}'
    email-pattern: '{email}'
    registration-number-pattern: '{uid}'
    identity-providers:
        - metadata: http://saml:8080/simplesaml/saml2/idp/metadata.php
          registration-id: testidp
          entity-id: artemis
          cert-file: # data/saml/cert (optional) Set this path to the Certificate for encryption/signing or leave it blank
          key-file: # data/saml/key path-to-key (optional) Set this path to the Key for encryption/ssigning or leave it blank

info.saml2.button-label: 'SAML Login'
info.saml2.enable-password: true
  1. (Enable Debug output)
  2. Start the stack using docker compose up -d
  3. Log in with SAML2 using user1 and user1pass
  4. User mail addresses are fixed, testing is in this configuration only possible when overwriting the user information in the SAML docker.