Currently, the Bitbucket integration UI only supports username/password authentication. However, token-based authentication (client ID/secret) appears to already be supported at the Helm chart level.

This suggests the limitation may be UI-only. It would be helpful to expose client ID/secret auth in the UI to align with existing backend capabilities and improve security/flexibility.

If this is just a UI gap, it could be a relatively quick win if prioritized.