Description of problem:

After upgrading the Bitbucket server to version 8.19.14, previously configured Personal Access Tokens no longer authenticate. The token has been verified to work with the server using both `git` and `curl` commands to validate.

Current workaround is to manually clone the repository locally and add it as a directory to the Dev Space

Prerequisites (if any, like setup, operators/versions):

• Red Hat OpenShift Container Platform 4.15.24
• Red Hat OpenShift Dev Spaces 3.17.0
• Bitbucket Server 8.19.14

Steps to Reproduce

• Add a personal access token for a user on the Bitbucket Server via the web UI
• Attempt to create a workspace using a valid repository from the server

Actual results:

Authentication errors, such as:

Unexpected devfile exception: Could not reach devfile at Server returned HTTP response code: 401 for URL

Expected results:

Successful clone of git repository from Bitbake server

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

devspaces pod logs with debugging enabled that demonstrate the authentication attempts using the token, and the secrets with the token redacted will be attached to the case privately