Skip to content

Getting Started with Rancher


Gluu Flex (“Flex”) is a cloud-native digital identity platform that enables organizations to authenticate and authorize people and software through the use of open standards like OpenID Connect, OAuth, and FIDO.

It is a downstream commercial distribution of the Linux Foundation Janssen Project software, plus a web administration tool(Gluu Admin-UI).

SUSE Rancher’s helm-based deployment approach simplifies the deployment and configuration of Flex, enabling organizations to take advantage of Flex’s modular design to improve their security posture while simultaneously enabling just-in-time auto-scaling.

The key services of Flex include:

  • (REQUIRED) Jans Auth Server: This component is the OAuth Authorization Server, the OpenID Connect Provider, and the UMA Authorization Server for person and software authentication. This service must be Internet-facing.

  • (REQUIRED) Jans Config API: The API to configure the auth-server and other components is consolidated in this component. This service should not be Internet-facing.

  • Gluu Admin UI: Web admin tool for ad-hoc configuration.

  • Jans Fido: This component provides the server-side endpoints to enroll and validate devices that use FIDO. It provides both FIDO U2F (register, authenticate) and FIDO 2 (attestation, assertion) endpoints. This service must be Internet-facing.

  • Jans SCIM: System for Cross-domain Identity Management (SCIM) is JSON/REST API to manage user data. Use it to add, edit and update user information. This service should not be Internet-facing.

  • Jans Casa: A self-service web portal for end-users to manage authentication and authorization preferences for their account in the Gluu Flex server. Typically, it enables people to manage their MFA credentials, like FIDO tokens and OTP authenticators. It's also extensible if your organization has any other self-service requirements.

Building Blocks#



In this Quickstart Guide, we will:

  1. Deploy Flex and add some users.
  2. Enable two-factor authentication.
  3. Protect content on an Apache web server with OpenID Connect.


This document is intended for DevOps engineers, site reliability engineers (SREs), platform engineers, software engineers, and developers who are responsible for managing and running stateful workloads in Kubernetes clusters.

Technical overview#


In addition to the core services listed in the Introduction above, the SUSE Rancher deployment includes the following components:

  • PostgreSQL/MySQL: SQL database dialect used to store configuration, people clients, sessions and other data needed for Gluu Flex operation.
  • Cert Manager: Used for managing X.509 certificates and crypto keys lifecycle in Janssen Server.
  • Key Rotation: A cronjob that implements Cert Manager to rotate the auth keys
  • Configuration job: loads (generate/restore) and dumps (backup) the configuration and secrets.
  • Persistence job: This job loads initial data for the backend used (SQL, LDAP, or Couchbase).
  • ConfigMaps: Stores configuration needed for Flex environment setup.
  • Secrets: Contains sensitive or confidential data such as a password, a token, or a key.

Config and Secret keys#

The Configuration job creates a set of configurations and secrets used by all services in the Flex setup.

To check the values of the configuration keys(configmaps) in the installation:

kubectl get cm cn -o json -n <namespace>

To check the values of the secret keys in installation:

kubectl get secret cn -o json -n <namespace>

Gluu Config Keys#

Key Example Values
admin_inum d3afef58-c026-4514-9d4c-e0a3efb4c29d
admin_ui_client_id 1901.a6575c1e-4688-4c11-8c95-d9e570b13ee8
auth_enc_keys RSA1_5 RSA-OAEP
auth_key_rotated_at 1653517558
auth_legacyIdTokenClaims false
auth_openidScopeBackwardCompatibility false
auth_openid_jks_fn /etc/certs/auth-keys.jks
auth_openid_jwks_fn /etc/certs/auth-keys.json
casa_client_id 0008-db36db1f-025e-4164-aeed-f82df064eee8
auth_sig_keys RS256 RS384 RS512 ES256 ES384 ES512 PS384 PS512
city Austin
country_code US
default_openid_jks_dn_name CN=Janssen Auth CA Certificate
fido2ConfigFolder /etc/jans/conf/fido2
jca_client_id 1801.4df6c3ba-ebf6-4836-8fb5-6da927586f61
optional_scopes [\"casa\", \"sql\", \"fido2\", \"scim\"]
orgName Gluu
tui_client_id 2000.9313cd4b-147c-4a67-96be-8a69ddbaf7e9
scim_client_id 1201.1cbcc731-3fca-4668-a480-1b5f5a7d6a53
state TX
token_server_admin_ui_client_id 1901.57a858dc-69f3-4967-befe-e089fe376638

Gluu Secret Keys#

Key Example Values
admin_ui_client_encoded_pw QlBMMTZUZWVYeWczVlpNUk1XN0pzdzrg
admin_ui_client_pw WnJYZEcyVlNBWG9d
auth_jks_base64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
auth_openid_jks_pass TWZoR3Rlb0NnUHEP
auth_openid_key_base64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
casa_client_encoded_pw b3NabG9oVGNncFVVWFpxNEJMU3V0dzrg
casa_client_pw M1g0Z1dEbGNPQ19d
encoded_admin_password e3NzaGF9eGpOaDRyblU3dzJZbmpPclovMUlheTdkR0RrOTdLe
jca_client_encoded_pw Um9NSEJnOU9IbTRvRkJHVVZETVZIeX58
jca_client_pw Um9NSEJnOU9IbTRvR
otp_configuration xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
pairwiseCalculationKey ZHd2VW01Y3VOUW6638ZHd2VW
pairwiseCalculationSalt ZHd2VW01Y3VOUW6638ZHd2VW0
plugins_admin_ui_properties xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
tui_client_encoded_pw ZHd2VW01Y3VOUW66388PS512
tui_client_pw AusZHd2VW01Y3VOUW6638
scim_client_encoded_pw UZHd2VW01Y3VOUW6638ZHd2VW01Y3VOUW6638
scim_client_pw ZHd2VW01Y3VOUW6638
sql_password ZHd2VW01Y3V638
ssl_ca_cert xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ssl_ca_key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ssl_cert xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ssl_csr xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ssl_key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
super_gluu_creds xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx3
token_server_admin_ui_client_encoded_pw Q1Z1cmtYWUlYSVg4U2tLTldVcnZVTUF
token_server_admin_ui_client_pw ZHd2VW01Y3VOUW6638


  • SUSE Rancher installed with an accessible UI

  • Kubernetes cluster running on SUSE Rancher with at least 1 worker node

  • Sufficient RBAC permissions to deploy and manage applications in the cluster.

  • LinuxIO kernel modules on the worker nodes

  • Docker running locally (Linux preferred)

  • Essential tools and CLI utilities are installed on your local workstation and are available in your $PATH: curl, kubectl

  • An entry in the /etc/hosts file of your local workstation to resolve the hostname of the Gluu Flex installation. This step is for testing purposes.


Summary of steps:

  1. Install Database:


    For the Database test setup to work, a PV provisioner support must be present in the underlying infrastructure.

    Install PostgreSQL database#


    If you are willing to use MySQL installation, skip this section and head to the Install MySQL section.

    To install a quick setup with PostgreSQL as the backend, you need to provide the connection parameters of a fresh setup. For a test setup, you can follow the below instructions:

    • Apps --> Charts and search for Postgres.
    • Click on Install on the right side of the window.
    • Create a new namespace called postgres and hit Next.
    • You should be on the Edit YAML page. Modify the below keys as desired. These values will be inputted in the installation of Gluu Flex
    • Click Install at the bottom right of the page.

    Install MySQL database#


    Skip this section if you installed PostgreSQL. This section is only needed if you are willing to use MySQL.

    To install a quick setup with MySQL as the backend, you need to provide the connection parameters of a fresh setup. For a test setup, you can follow the below instructions:

    • Open a kubectl shell from the top right navigation menu >_.
    • Run:
      helm repo add bitnami
      helm repo update
      kubectl create ns gluu #Create gluu namespace
    • Pass in a custom password for the database. Here we used Test1234#. The admin user will be left as root. Notice we are installing in the gluu namespace. Run

      helm install my-release --set auth.rootPassword=Test1234#,auth.database=jans bitnami/mysql -n gluu

    Successful Installation#

    After the installation is successful, you should have a Statefulset active in the rancher UI as shown in the screenshot below.

    Screenshot 2022-07-05 at 14 54 26

  2. Install Nginx-Ingress, if you are not using Istio ingress

    helm repo add ingress-nginx
    helm repo add stable
    helm repo update
    helm install nginx ingress-nginx/ingress-nginx

    To get the Loadbalancer IP:

    kubectl get svc nginx-ingress-nginx-controller --output jsonpath='{.status.loadBalancer.ingress[0].ip}'

  3. Install Gluu Flex:

    • Head to Apps --> Charts and search for Gluu
    • Click on Install on the right side of the window.
    • Change the namespace from default to gluu, then click on Next.
    • Scroll through the sections to get familiar with the options. For minimal setup follow with the next instructions.
    • Add License SSA. Before initiating the setup, please obtain an SSA for Flex trial, after which you will issued a JWT.
    • Click on the Persistence section. Change SQL database host uri to postgresql.postgres.svc.cluster.local in the case of PostgreSQL or my-release-mysql.gluu.svc.cluster.local in the case of MySQL. Also set SQL database username,SQL password, and SQL database name to the values you used during the database installation.
    • To enable Casa and the Admin UI, navigate to the Optional Services section and check the Enable casa and boolean flag to enable admin UI boxes. You can also enable different services like Client API and Jackrabbit.
    • Click on the section named Ingress and enable all the endpoints. You might add LB IP or address if you don't have FQDN for Gluu.
    • To pass your FQDN or Domain that is intended to serve the Gluu Flex IDP, head to the Configuration section:
      1. Add your FQDN and check the box Is the FQDN globally resolvable.
      2. Click on the Edit YAML tab and add your FQDN to nginx-ingress.ingress.hosts and nginx-ingress.ingress.tls.hosts.
    • Click on Install on the bottom right of the window.


    You can upgrade your installation after the deployment. To do that, go to the SUSE Rancher Dashboard -> Apps -> Installed Apps -> gluu -> Click on the 3 dots on the right -> Upgrade -> Make your changes -> Click Update.

The running deployment and services of different Gluu Flex components like casa, admin-ui, scim, auth-server, etc can be viewed by navigating through the SUSE Rancher. Go to Workloads and see the running pods. Go under Service Discovery and checkout the Ingresses and Services. All deployed components should be in a healthy and running state like in the screenshot shown below.

Screenshot 2022-07-05 at 11 53 06

Connecting to the Setup#


You can skip this section if you have a globally resolvable FQDN.

In the event you used microk8s or your fqdn is not registered, the below steps will help with connecting to your setup.

  1. To access the setup from a browser or another VM, we need to change the ingress class annotation from nginx to public e.g., for the specific component you want to access publicly in the browser;

    • Navigate through the SUSE Rancher UI to Service Discovery -> Ingresses
    • Choose the ingress for the targeted component. For example gluu-nginx-ingress-auth-server for auth-server
    • Click on the three dots in the top right corner
    • Click on Edit Yaml
    • On line 8, change the annotation value from nginx to public
    • Click Save

    Screenshot 2022-07-05 at 11 54 17

  2. The LoadBalancer IP needs to get mapped inside /etc/hosts with the domain chosen for gluu flex. If the domain you used in the setup is
  3. You can do the same edit for every component you want to access publicly from the browser.

Testing Configuration endpoints#

  1. Try accessing some Gluu Flex endpoints like in the browser and you'll get back a JSON response;

    Screenshot 2022-07-17 at 02 27 17

  2. Note that you can also access those endpoints via curl command, E.g.

    curl -k

    You should get a similar response like the one below;


Login and Add a New User#

After inputting the license keys, you can then use admin and the password you set to login to the Admin UI and you should see the Admin UI dashboard.

You could also add another test user via the admin UI that will be used for testing Casa and 2FA as shown in the screenshot below.

Navigate to Users and click on + in the top right corner to add a user.

Screenshot 2022-07-26 at 15 51 58

Testing Casa#

Jans Casa ("Casa") is a self-service web portal for managing account security preferences. The primary use case for Casa is self-service 2FA, but other use cases and functionalities can be supported via Casa plugins.

Although you have not enabled two-factor authentication yet, you should still be able to login to Casa as the admin user and the password is the one you set during installation.

Point your browser to and you should be welcomed by the Casa login page as shown below.

Screenshot 2022-07-06 at 22 39 49

After logging in, you'll be welcomed by the home page as shown below.

Screenshot 2022-08-24 at 19 13 24

Enabling Two-Factor Authentication#

In this part, we are going to enable two standard authentication mechanisms: OTP and FIDO.

This can be done through the admin UI. 2FA can be turned on by clicking the switch in the Second Factor Authentication widget. By default, you will be able to choose from a few 2FA policies:

  • Always (upon every login attempt)
  • If the location (e.g. city) detected in the login attempt is unrecognized
  • If the device used to login is unrecognized

To reduce the chance of account lockout, enroll at least two different types of 2FA credentials -- e.g. one security key and one OTP app; or one OTP app and one SMS phone number, etc. This way, regardless of which device you're using to access a protected resource, you will have a usable option for passing strong authentication.

To enable 2FA, firstly the OTP and FIDO components have to be enabled in the Casa admin UI then login to Casa as an end user, and register an OTP device (i.e. Google Authenticator) and a FIDO device.

Register OTP device

  • To add a new OTP token, navigate to 2FA credentials > OTP Tokens.
  • You can either add a soft OTP token by choosing the Soft token option or a hard token by choosing the Hard Token Option
  • Check the soft OTP token and click ready
  • Before proceeding to the next step, Download Google Authenticator from Google Play or Appstore
  • Then proceed and scan the QR code with your app

Screenshot 2022-08-29 at 10 18 43

  • Enter the 6-digit code that appears in your authenticator app and validate the enrollment.

Register Fido device

  • To add a new FIDO 2 credential, navigate to 2FA credentials > Security Keys and built-in Platform Authenticators Insert the fido key and click Ready. Casa will prompt you to press the button on the key.

Screenshot 2022-08-29 at 10 42 42

  • Add a nickname and click Add. Once added, the new device will appear in a list on the same page. Click the pencil to edit the device's nickname

Testing Apache OIDC Locally#

In this part, we are going to use docker to locally configure an apache web server, and then install the mod_auth_openidc module and configure it accordingly.

Using local docker containers, our approach is to first register a client, then spin up two Apache containers, one serving static content (with server-side includes configured so we can display headers and environment information), and one acting as the OpenID Connect authenticating reverse proxy.

Register an OpenID Connect client#

On the Janssen server, you can register a new client in the Flex Admin UI or the jans-cli. In this section, we are going to show both ways of doing it from the Admin UI and using jans-cli

Admin UI#

Navigate to Auth server -> Clients and click on + in the top right corner to create a client.

Take note of the following keys:values because they configure the right client that we need

scopes: email_,openid_,profile
responseTypes: code

The screenshot below shows an example of the Admin UI section from where a client is created

Screenshot 2022-07-26 at 16 34 05

Jans TUI#

On the Janssen server, we are going to register a new client using the jans-cli. There are two ways you can register an OIDC client with the Janssen server, Manual Client Registration and Dynamic Client Registration (DCR).

Here we will use manual client registration. We will use jans-tui tool provided by the Janssen server. jans-tui has a menu-driven interface that makes it easy to configure the Janssen server. Here we will use the menu-driven approach to register a new client.

  1. Download jans-cli-tui from the release assets depending on your OS. For example:


    Now we have jans-cli-tui-linux-ubuntu-X86-64.pyz downloaded.

  2. Now we can grab the FQDN, client-id, client-secret, and connect using the following commands:

    FQDN= #Add your FQDN here
    TUI_CLIENT_ID=$(kubectl get cm cn -n <namespace> --template={{.data.tui_client_id}})
    TUI_CLIENT_SECRET=$(kubectl get secret cn -n <namespace> --template={{.data.tui_client_pw}} | base64 -d)
    #add -noverify if your FQDN is not registered

  3. Get schema file using this command

    python3 jans-cli-tui-linux-ubuntu-X86-64.pyz --host <FQDN> --client-id <TUI_CLIENT_ID> --client-secret <TUI_CLIENT_SECRET> --no-tui --schema /components/schemas/Client

  4. Add values for required params and store this JSON in a text file. Take keynote of the following properties.


        "dn": null,
        "inum": null,
        "displayName": "<name-of-choice>",
        "clientSecret": "<secret-of-your-choice>",
        "frontChannelLogoutUri": null,
        "frontChannelLogoutSessionRequired": null,
        "registrationAccessToken": null,
        "clientIdIssuedAt": null,
        "clientSecretExpiresAt": null,
        "redirectUris": [
        "claimRedirectUris": null,
        "responseTypes": [
        "grantTypes": [
        "applicationType": "web",
        "contacts": null,
        "idTokenTokenBindingCnf": null,
        "logoUri": null,
        "clientUri": null,
        "policyUri": null,
        "tosUri": null,
        "jwksUri": null,
        "jwks": null,
        "sectorIdentifierUri": null,
        "subjectType": "public",
        "idTokenSignedResponseAlg": null,
        "idTokenEncryptedResponseAlg": null,
        "idTokenEncryptedResponseEnc": null,
        "userInfoSignedResponseAlg": null,
        "userInfoEncryptedResponseAlg": null,
        "userInfoEncryptedResponseEnc": null,
        "requestObjectSigningAlg": null,
        "requestObjectEncryptionAlg": null,
        "requestObjectEncryptionEnc": null,
        "tokenEndpointAuthMethod": "client_secret_basic",
        "tokenEndpointAuthSigningAlg": null,
        "defaultMaxAge": null,
        "requireAuthTime": null,
        "defaultAcrValues": null,
        "initiateLoginUri": null,
        "postLogoutRedirectUris": null,
        "requestUris": null,
        "scopes": [
        "claims": null,
        "trustedClient": false,
        "lastAccessTime": null,
        "lastLogonTime": null,
        "persistClientAuthorizations": null,
        "includeClaimsInIdToken": false,
        "refreshTokenLifetime": null,
        "accessTokenLifetime": null,
        "customAttributes": null,
        "customObjectClasses": null,
        "rptAsJwt": null,
        "accessTokenAsJwt": null,
        "accessTokenSigningAlg": null,
        "disabled": false,
        "authorizedOrigins": null,
        "softwareId": null,
        "softwareVersion": null,
        "softwareStatement": null,
        "attributes": null,
        "backchannelTokenDeliveryMode": null,
        "backchannelClientNotificationEndpoint": null,
        "backchannelAuthenticationRequestSigningAlg": null,
        "backchannelUserCodeParameter": null,
        "expirationDate": null,
        "deletable": false,
        "jansId": null,
        "description": null
  5. Now you can use that JSON file as input to the command below and register your client

    python3 jans-cli-tui-linux-ubuntu-X86-64.pyz --host <FQDN> --client-id <TUI_CLIENT_ID> --client-secret <TUI_CLIENT_SECRET> --no-tui --operation-id=post-oauth-openid-client --data <path>/schema-json-file.json

  6. After the client is successfully registered, there will be data that describes the newly registered client. Some of these values, like inum and clientSecret, will be required before we configure mod_auth_openidc So keep in mind that we shall get back to this.

Create an Application Container#

An application docker container will be run locally which will act as the protected resource (PR) / external application. The following files have code for the small application. We shall create a directory locally / on your machine called test and add the required files.

  1. Firstly create a project folder named test by running mkdir test && cd test and add the following files with their content;


    ServerRoot "/usr/local/apache2"
    Listen 80
    LoadModule mpm_event_module modules/
    LoadModule authz_core_module modules/
    LoadModule include_module modules/
    LoadModule filter_module modules/
    LoadModule mime_module modules/
    LoadModule log_config_module modules/
    LoadModule setenvif_module modules/
    LoadModule unixd_module modules/
    LoadModule dir_module modules/
    User daemon
    Group daemon
    <Directory />
    AllowOverride none
    Require all denied
    DocumentRoot "/usr/local/apache2/htdocs"
    <Directory "/usr/local/apache2/htdocs">
    Options Indexes FollowSymLinks Includes
    AllowOverride None
    Require all granted
    SetEnvIf X-Remote-User "(.*)" REMOTE_USER=$0
    SetEnvIf X-Remote-User-Name "(.*)" REMOTE_USER_NAME=$0
    SetEnvIf X-Remote-User-Email "(.*)" REMOTE_USER_EMAIL=$0
    DirectoryIndex index.html
    <Files ".ht*">
        Require all denied
    ErrorLog /proc/self/fd/2
    LogLevel warn
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    CustomLog /proc/self/fd/1 common
    TypesConfig conf/mime.types
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml


    <title>Hello User</title>
    <p>Hello <!--#echo var=REMOTE_USER_NAME -->!</p>
    <p>You authenticated as: <!--#echo var=REMOTE_USER --></p>
    <p>Your email address is: <!--#echo var=REMOTE_USER_EMAIL --></p>
    <p><!--#printenv -->!</p>


    <title>Hello World</title>
    <p>Hello world!</p>


    FROM httpd:2.4.54@sha256:c9eba4494b9d856843b49eb897f9a583a0873b1c14c86d5ab77e5bdedd6ad05d
    # "Created": "2022-06-08T18:45:46.260791323Z" , "Version":"2.4.54"
    RUN apt-get update \
    && apt-get install -y --no-install-recommends wget ca-certificates libcjose0 libhiredis0.14 apache2-api-20120211 apache2-bin\
    && wget \
    && dpkg -i libapache2-mod-auth-openidc_2.4.11.2-1.buster+1_amd64.deb \
    && ln -s /usr/lib/apache2/modules/ /usr/local/apache2/modules/ \
    && rm -rf /var/log/dpkg.log /var/log/alternatives.log /var/log/apt \
    && touch /usr/local/apache2/conf/extra/secret.conf \
    && touch /usr/local/apache2/conf/extra/oidc.conf
    RUN echo "\n\nLoadModule auth_openidc_module modules/\n\nInclude conf/extra/secret.conf\nInclude conf/extra/oidc.conf\n" >> /usr/local/apache2/conf/httpd.conf


    OIDCClientID <inum-as-received-in-client-registration-response>
    OIDCCryptoPassphrase <crypto-passphrase-of-choice>
    OIDCClientSecret <as-provided-in-client-registration-request>
    OIDCResponseType code
    OIDCScope "openid email profile"
    OIDCProviderTokenEndpointAuth client_secret_basic
    OIDCSSLValidateServer Off
    OIDCRedirectURI http://localhost:8111/oauth2callback
    OIDCCryptoPassphrase <crypto-passphrase-of-choice>
    <Location "/">
        Require valid-user
        AuthType openid-connect
  2. After, run an Apache container which will play the role of an application being protected by the authenticating reverse proxy.

    docker run -dit -p 8110:80 \
           -v "$PWD/app.conf":/usr/local/apache2/conf/httpd.conf \
           -v "$PWD/index.html":/usr/local/apache2/htdocs/index.html \
           -v "$PWD/user.shtml":/usr/local/apache2/htdocs/user.shtml \
           --name apache-app httpd:2.4

    Note that we are using a popular pre-built image useful for acting as a reverse proxy for authentication in front of an application. It contains a stripped-down Apache with minimal modules, and adds the mod_auth_openidc module for performing OpenID Connect authentication.

  3. Make a test curl command call to ensure you get back some content as shown in the screenshot below

    curl http://localhost:8110/user.shtml

    Screenshot 2022-07-05 at 23 30 25

Create an Authenticating Reverse Proxy Container#

We shall use Apache, but this time we use a Docker image that has mod_auth_oidc installed and configured. This proxy will require authentication, handle the authentication flow with redirects, and then forward requests to the application.

In order to use this, you will need to have registered a new OpenID Connect client on the Janssen server. We did that in the step 1 above

  1. Add the following files to the test folder.


    # Unset to make sure clients can't control these
    RequestHeader unset X-Remote-User
    RequestHeader unset X-Remote-User-Name
    RequestHeader unset X-Remote-User-Email
    # If you want to see tons of logs for your experimentation
    #LogLevel trace8
    OIDCClientID <inum-as-received-in-client-registration-response>
    OIDCRedirectURI http://localhost:8111/oauth2callback
    OIDCScope "openid email profile"
    OIDCRemoteUserClaim principal
    OIDCPassClaimsAs environment
    <Location />
    AuthType openid-connect
    Require valid-user
    ProxyPass http://app:80/
    ProxyPassReverse http://app:80/
    RequestHeader set X-Remote-User %{OIDC_CLAIM_principal}e
    RequestHeader set X-Remote-User-Name %{OIDC_CLAIM_name}e
    RequestHeader set X-Remote-User-Email %{OIDC_CLAIM_email}e


    # This is the main Apache HTTP server configuration file. For documentation, see:
    # This is intended to be a hardened configuration, with minimal security surface area necessary
    # to run mod_auth_openidc.
    ServerRoot "/usr/local/apache2"
    Listen 80
    LoadModule mpm_event_module modules/
    LoadModule authn_file_module modules/
    LoadModule authn_core_module modules/
    LoadModule authz_host_module modules/
    LoadModule authz_groupfile_module modules/
    LoadModule authz_user_module modules/
    LoadModule authz_core_module modules/
    LoadModule access_compat_module modules/
    LoadModule auth_basic_module modules/
    LoadModule reqtimeout_module modules/
    LoadModule filter_module modules/
    LoadModule mime_module modules/
    LoadModule log_config_module modules/
    LoadModule env_module modules/
    LoadModule headers_module modules/
    LoadModule setenvif_module modules/
    #LoadModule version_module modules/
    LoadModule proxy_module modules/
    LoadModule proxy_http_module modules/
    LoadModule unixd_module modules/
    #LoadModule status_module modules/
    #LoadModule autoindex_module modules/
    LoadModule dir_module modules/
    LoadModule alias_module modules/
    <IfModule unixd_module>
        User daemon
        Group daemon
    <Directory />
        AllowOverride none
        Require all denied
    DocumentRoot "/usr/local/apache2/htdocs"
    <Directory "/usr/local/apache2/htdocs">
        Options Indexes FollowSymLinks
        AllowOverride None
        Require all granted
    <IfModule dir_module>
        DirectoryIndex index.html
    <Directory /opt/apache/htdocs>
        Options None
        Require all denied
    <Files ".ht*">
        Require all denied
    ErrorLog /proc/self/fd/2
    LogLevel warn
    <IfModule log_config_module>
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
        CustomLog /proc/self/fd/1 common
    <IfModule alias_module>
        ScriptAlias /cgi-bin/ "/usr/local/apache2/cgi-bin/"
    <Directory "/usr/local/apache2/cgi-bin">
        AllowOverride None
        Options None
        Require all granted
    <IfModule headers_module>
        RequestHeader unset Proxy early
    <IfModule mime_module>
        TypesConfig conf/mime.types
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
    <IfModule proxy_html_module>
    Include conf/extra/proxy-html.conf
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    TraceEnable off
    ServerTokens Prod
    ServerSignature Off
    LoadModule auth_openidc_module modules/
    Include conf/extra/secret.conf
    Include conf/extra/oidc.conf
  2. Edit the file to include the client secret for the client you created during DCR, and add a securely generated pass phrase for the session keys

    docker build --pull -t apache-oidc -f Dockerfile .
    docker run -dit -p 8111:80 \
           -v "$PWD/proxy.conf":/usr/local/apache2/conf/httpd.conf \
           -v "$PWD/gluu.secret.conf":/usr/local/apache2/conf/extra/secret.conf \
           -v "$PWD/oidc.conf":/usr/local/apache2/conf/extra/oidc.conf \
           --link apache-app:app \
           --name apache-proxy apache-oidc
  3. Now open a fresh web browser with private (incognito) mode, and go to this url

  4. To check the proxy logs

    docker logs -f apache-proxy
  5. To see the app logs

    docker logs -f apache-app
  6. If you modified the configuration files, just restart the proxy.

    docker restart apache-proxy

Last update: 2024-07-04
Created: 2023-01-25