BFG configured for AT-TLS shows blank landing page

Products

• Endevor

Issue/Introduction

Endevor Bridge for Git (BFG) 2.15.10

Can get to BFG landing page unsecured but if secure port 8081 is using AT-TLS the loaded page (https://bfg.example.com:8081) is blank.
There is no error/handshake error when TLS trace is enabled.
Using oauth2.

Environment

Endevor Bridge For Git

Resolution

From a BFG point of view AT-TLS should be considered as a reverse proxy - proxying from http to https.
Relevant doc. page: Endevor® Bridge for Git 2.0 > Installing > Configure Additional Installation Options > Configure a Proxy Server > Reverse Proxy Server.

The ssl section parameters had been configured in the application.yml file and they should not be used.

Configure the reverse proxy server in the application.yml file as follows:

1. Do not specify any ssl options in the application.yml i.e. do not use native TLS, because AT-TLS is used instead.
   So first comment out the ssl section in the application.yml file i.e.
   *****
   #  ssl:
#    key-store-type:
#    key-store:
#    key-store-password:
#    key-alias:
   *****
   
   
2. Configure https reverse proxy setup (note port 8081 was being used for this particular configuration):
   *****
   app:
  git-bridge:
    url: https://bfg.example.com:8081
   *****
   
   
3. Under Bitbucket:
   app:
  bitbucket:
    oauth2:
        override-redirect: true
   (Even though the doc. page does only mentions 'override-redirect: true' under oauth, it is also required for oauth2)