Problem

The documentation for activating Okta OIDC social authentication indicates that when I set the three following environment variables, the login screen will have an option to authenticate using Okta OIDC:

1. OAUTH_OKTA_OPENIDCONNECT_KEY
2. OAUTH_OKTA_OPENIDCONNECT_SECRET
3. OAUTH_OKTA_OPENIDCONNECT_API_URL

This is not happening.

How to reproduce the behaviour

1. Run doccano:1.2.1 image with the following command:

docker run --rm --interactive --tty
    --env SECRET_KEY=REDACTED \
    --env [email protected] \
    --env ADMIN_PASSWORD=REDACTED \
    --env ADMIN_USERNAME=admin \
    --env OAUTH_OKTA_OPENIDCONNECT_KEY=REDACTED \
    --env OAUTH_OKTA_OPENIDCONNECT_SECRET=REDACTED \
    --env OAUTH_OKTA_OPENIDCONNECT_API_URL=https://my-identity.okta.com/api \
    --publish 8000:8000 \
    doccano/doccano:1.2.1

2. Navigate to doccano in your browser at: http://locahost:8000
3. Select the "login" button at the top-right of the page

Expected behavior

I expect to see the "Login with Okta" option as depicted in this image

Actual behavior

I end up seeing the same login screen/options that I get when I do not configure Okta OIDC social authentication.

My environment

• I am running the doccano/doccano:1.2.1 Docker image
• I am running behind a enterprise firewall with a SSL packet inspection and enterprise certificate authority. Other applications can perform Okta OIDC SSO in this environment, but app eventually needs to recognize system installed trusted CA chain. I do not expect this to be the source of this problem before we actually submit login credentials, however - there is a possibility.
• docker-desktop v20.10.5 on Windows 10
• Above command issued from WSL version 1, running WSL (version 1 with Ubuntu 18.04 LTS) bash:

$ uname -a
Linux MY-PC 4.4.0-18362-Microsoft #1049-Microsoft Thu Aug 14 12:01:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux