# Okta as SAML IDP for SSO

# Preamble

The EE server and client support the SAML protocol that allows you to configure an external service as IDP (identity provider) for SSO (single sign on). This guide here will explain how to configure Okta as SAML IDP for SSO. We assume that your webclient is running on https://example.com, the server is reachable with https://example.com/server (e.g. https://example.com/server/info/ shows you some nice json output). This is your first SAML provider that you want to configure (therefore we give him the ID "1").


This feature is only available in the Enterprise Edition.

# Okta

As a first step we have to configure Okta.

  1. Go to Applications

    Got to applications

  2. Click "Add Application"

    Click "Add application"

  3. Click "Create New App"

    Click "Create New App"

  4. Select "Web" and "Saml 2.0"

    Select "Web" and "Saml 2.0"

  5. Enter Name in "General Settings"

    Enter Name in "General Settings"

  6. Configure SAML

    Configure SAML as shown below. Adjust the URLs according to your domain (and if necessary according to your SAML provider ID)

    Configure SAML

  7. Feedback

    Click "I'm an Okta customer adding an internal app" and fill in the necessary information in order to pass this screen.


  8. Click "View Setup Instructions"

    Click "View Setup Instructions"

  9. Remember "Setup Instructions"

    You should see now a screen as shown below.

    Click "View Setup Instructions"


    Download / Remember these information, you will need them in the next step.

  10. Go to "Assignments"

    Assign users and groups who should be able to use Psono.

    Assign users and groups

# Server (settings.yaml)

During the installation of the server you have created a settings.yaml that needs to be adjusted now.

  1. Generate SP certificate

    You will need a certificate for your service provider (SP) later. You can generate one easily with:

    openssl req -new -newkey rsa:2048 -x509 -days 3650 -nodes -sha256 -out sp_x509cert.crt -keyout sp_private_key.key

    This will generate a private key (sp_private_key.key) and the public certificate (sp_x509cert.crt).

  2. Comment in the following section:

                    binding: "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
                    url: ""
                    binding: "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
                    url: "OKTA_SSO_SIGN_IN_URL"
                x509cert: "OKTA_SSO_X509_CERTIFICATE"
                groups_attribute: "groups"
                username_attribute: "username"
                email_attribute: "email"
                username_domain: "example.com"
                required_group: []
                is_adfs: false
                honor_multifactors: true
                max_session_lifetime: 43200
                NameIDFormat: "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
                    binding: "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
                    serviceName: "SP_SERVICE_NAME"
                    serviceDescription: "Psono password manager"
                            attributeValue: []
                            friendlyName: ""
                            isRequired: false
                            name: "attribute-that-has-to-be-requested-explicitely"
                            nameFormat: ""
                privateKey: "SP_PRIVATE_CERTIFICATE"
                    binding: "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
                x509cert: "SP_X509CERT"
                autoprovision_psono_folder: false
                autoprovision_psono_group: false
            strict: true
    • Replace OKTA_SSO_SAML_IDENTITY_PROVIDER_ISSUE with the "Identity Provider Issuer" from Okta's previous "Setup Instructions".
    • Replace OKTA_SSO_SIGN_IN_URL with the "Identity Provider Single Sign-On URL" from kta's previous "Setup Instructions".
    • Replace OKTA_SSO_X509_CERTIFICATE with the "X.509 Certificate" from Okta's previous "Setup Instructions". (remove all line breaks)
    • Replace SP_SERVICE_NAME with the "metadata" URL of your service provider, e.g. https://example.com/server/saml/1/metadata/
    • Replace SP_PRIVATE_CERTIFICATE with the content of the previous generated "sp_private_key.key". (remove all line breaks)
    • Replace SP_X509CERT with the content of the previous generated "sp_x509cert.crt". (remove all line breaks)

    Restart the server afterward

  3. Adjust authentication methods

    Make sure that SAML is part of the AUTHENTICATION_METHODS parameter in your settings.yaml e.g.


    Restart the server afterward

  4. (optional) Debug Mode

    It is helpful in the later debugging to enable debug mode.

    DEBUG: True


    Restart the server afterward and don't forget to remove it before going to production.

# Client (config.json)

Now you have to configure your client, so your users can use this configured IDP.

  1. Basic

    Update your config.json similar to the one shown below.

        "authentication_methods": ["SAML"],
        "saml_provider": [{
          "title": "SAML Login",
          "provider_id": 1,
          "button_name": "Login "

    The variable authentication_methods restricts the allowed login methods. In the example above only SAML will be allowed and the normal login "hidden". The title and button_name can be adjusted however you like. The provider_id needs to match the one that you used on your server.

  2. (optional) Automatic login

    You may want to "automatically" click on the login button to initiate the login flow. You can accomplish this by modifying the config.json as shown below:

        "authentication_methods": ["SAML"],
        "auto_login": true,


    This will only work if you have just one provider configured with only one authentication method. Users won't be able to modify the server url nor choose to register or interact with the login form in any other way.