ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

B4G server not starting up using BitBucket inside of Azure App Gateway

book

Article ID: 240724

calendar_today

Updated On:

Products

Endevor Software Change Manager (SCM)

Issue/Introduction

Using B4G 2.10.2 with Bitbucket.

B4G server goes down at start:

2022-03-30 13:48:12.971 DEBUG 876975 --- [main] c.c.e.i.c.g.r.bitbucket.BitbucketClient  : Request: POST https://bitbucket.devopsdesa.credito.bcp.com.pe/plugins/servlet/oauth/request-token
2022-03-30 13:48:13.655 DEBUG 876975 --- [main] c.c.e.i.c.g.r.bitbucket.BitbucketClient  : 

com.google.api.client.http.HttpResponseException: 411 Length Required

Cause

Site has Azure Application Gateway in place to connect the servers.

Environment

Release : 18.1

Component : BRIDGE FOR GIT

Resolution

Resolved by -- 2.10.4 fix for BCP.zip ( this B4G version allows for login using PAT tokens that works inside the Azure App Gateway)

Two important notes:

- Need to add a parameter to the existing application.yml. Under app.security, add the following:
personal-access-token-login: true

- When running the server, ensure to clear the cache in the browser. Users will need to generate and supply PATs from Bitbucket on the login screen.