Tell us more.

Currently, when we configure a bitbucket-server using a token, we do fetch username attached to the token. I am not sure if a username is always present for a token or not .. I'll need to verify that.

We don't fetch the username like we do on other platforms because there is no dedicated api endpoint for it.

There seems to be a way to get the username thought by adding the header: X-AUSERNAME to any request that we make to the bitbucket-server API. ¹

The suggested way is to call the /rest/api/1.0/application-properties endpoint which never fails and attach the header with it to get user details related to the token from the response.

In the bitbucket-server code we conditionally make the request to application-properties endpoint here:

I think we should remove the condition and always make this call with the required header, so we can fetch username..except for the rare case when username is already configures and env.RENOVATE_X_PLATFORM_VERSION is also set.