Container behind load balancer sending back http prefix rather than https about docker-bookstack HOT 5 CLOSED

# The below url has to be set if using social auth options

# or if you are not using BookStack at the root path of your domain.

APP_URL=https://dev-wiki.fsu.com​

version: '2'
services:
 bookstack:
    image: solidnerd/bookstack:0.21.0
    restart: always
    environment:
    - DB_HOST=dsdfsdfsdf.cccskphrgnlg.us-xxx-1.rds.amazonaws.com:3306
    - DB_DATABASE=bookstack
    - DB_USERNAME=secretuser
    - DB_PASSWORD=secretpassword
    env_file: .env
    volumes:
    - uploads:/var/www/bookstack/public/uploads
    - storage-uploads:/var/www/bookstack/public/storage
    ports:
    - "8080:80"

volumes:
 uploads:
 storage-uploads:

To summarize our call, we identified the  GET /authorize request/response to and from Okta to your application from the chrome browser dev tools. We also saw that the 'code' response was sent to https://dev-wiki.forescoutuniversity.com/login/service/okta/callback.

And from Okta logs, we captured the logs pertaining to /oauth2/v1/token request showing that the tokens were sent in the response successfully.

The issue could be at the application end. Hence I request you to troubleshoot more on how the application handles the tokens returned by Okta and what it does next to figure out who is redirecting to http://dev-wiki.forescoutuniversity.com. 

More pointers:

Like discussed, in the Authorization Code Flow, we have two steps,

1. GET /authorize to get the code in the redirect_uri (https://developer.okta.com/docs/api/resources/oidc#authorize)
2. POST to /oauth2/v1/token endpoint along with code to get the tokens (https://developer.okta.com/docs/api/resources/oidc#token)

You can find more information here: 

https://developer.okta.com/authentication-guide/implementing-authentication/auth-code