OpenID Connect Provider Certification

The OpenID Foundation provides a set of conformance test profilesthat test both Relying Party and OpenID Provider (OP) OpenID Connect implementations. Upon submission of resultsand an affirmative response, the affirmed OP will be listed as a certified OPon the OpenID Connect website and allowed to use the certification markaccording to the certification terms and conditions, section 3(d).

Basic OpenID Provider Tests

Dex is an OP that strives to implement the mandatory setof OpenID Connect features, and can be tested against the Basic OpenID Provider profile ( profile outline, section 2.1.1). These tests ensure that all features required by a basic clientwork as expected.

Features are currently under development to fully comply with the Basic profile, as dex currently does not. The following issues track our progress:

Setup

There are two ways to set up an OpenID test instance:

1. Configure a test instance provided by The OpenID Foundation by following instructionson their website.
2. Download their test runner from GitHuband follow the instructions in the README.
   • Requires docker and docker-compose

Configuration is essentially the same for either type of OpenID test instance. We will proceed with option 1 in this example, and set up an AWS EC2 instanceto deploy dex:

• Create an AWS EC2 instanceand connect to your instance using SSH.
• Install dex .
• Ensure whatever port dex is listening on (usually 5556) is open to ingress traffic in your security group configuration.
• In this example the public DNS name, automatically assigned to each internet-facing EC2 instance, is my-test-ec2-server.com. You can find your instances’ in the AWS EC2 management console.

Configuring an OpenID test instance

1. Navigate to https://op.certification.openid.net:60000.
2. Click ‘New’ configuration.
3. Input your issuer url: http://my-test-ec2-server.com:5556/dex.
4. Select code as the response type.
5. Click ‘Create’ to further configure your OpenID instance.
6. On the next page, copy and paste the redirect_uris into the redirectURIs config field (see below).

7. At this point we can run dex, as we have all the information necessary to create a config file (oidc-config.yaml in this example):

   issuer: http://my-test-ec2-server.com:5556/dex
   storage:
     type: sqlite3
     config:
       file: examples/dex.db
   web:
     http: 0.0.0.0:5556
   oauth2:
     skipApprovalScreen: true
   staticClients:
   - id: example-app
     redirectURIs:
     - 'https://op.certification.openid.net:${OPENID_SERVER_PORT}/authz_cb'
     name: 'Example App'
     secret: ZXhhbXBsZS1hcHAtc2VjcmV0
   connectors:
   - type: mockCallback
     id: mock
     name: Example

   • Substitute OPENID_SERVER_PORT for your OpenID test instance port number, assigned after configuring that instance.
   • Set the oauth2 field skipApprovalScreen: true to automate some clicking.

8. Run dex:

   $ ./bin/dex serve oidc-config.yaml
   time="2017-08-25T06:34:57Z" level=info msg="config issuer: http://my-test-ec2-server.com:5556/dex"
   ...

9. Input client_id and client_secret from your config file.

   • The id and secret used here are from the example config file staticClients field.

10. Use data returned by the GET /.well-known/openid-configuration API call to fill in the rest of the configuration forms:

    [home@localhost ~]$ curl http://my-test-ec2-server.com:5556/dex/.well-known/openid-configuration
    {
     "issuer": "http://my-test-ec2-server.com:5556/dex",
     "authorization_endpoint": "http://my-test-ec2-server.com:5556/dex/auth",
     "token_endpoint": "http://my-test-ec2-server.com:5556/dex/token",
     "jwks_uri": "http://my-test-ec2-server.com:5556/dex/keys",
     "response_types_supported": [
       "code"
     ],
     "subject_types_supported": [
       "public"
     ],
     "id_token_signing_alg_values_supported": [
       "RS256"
     ],
     "scopes_supported": [
       "openid",
       "email",
       "groups",
       "profile",
       "offline_access"
     ],
     "token_endpoint_auth_methods_supported": [
       "client_secret_basic"
     ],
     "claims_supported": [
       "aud",
       "email",
       "email_verified",
       "exp",
       "iat",
       "iss",
       "locale",
       "name",
       "sub"
     ]
    }

    • Fill in all configuration information that the /.well-known/openid-configuration endpoint returns, althgouh this is not strictly necessary. We should give the test cases as much information about dex’s OP implementation as possible.
11. Press the ‘Save and Start’ button to start your OpenID test instance.
12. Follow the provided link.
13. Run through each test case, following all instructions given by individual cases.
    • In order to pass certain cases, screenshots of OP responses might be required.

Results and Submission

Dex does not fully pass the Basic profile test suite yet. The following table contains the current state of test results.

Once all test cases pass, submit your results by following instructions listed on the website.