Support for BitBucket HTTPS Token due to SSO/SAML authentication restrictions

[raffertyuy]

Description

We need a way to migrate from BitBucket with SAML Authentication enabled. We believe this can be solved by supporting BitBucket HTTPS token which gh bb2sgh doesn't support.

(Unauthorized): {"errors":[{"context":null,"message":"Authentication failed. Please check your credentials and try again.","exceptionName":"com.resolution.atlasplugins.samlsso.bitbucket.userauth.OnlySAMLAuthenticationAllowedException"}]}

[timrogers]

@raffertyuy My understanding is that the export API that bbs2gh uses only supports usernames and passwords - so I'm not sure how we'd solve this.

Would you be willing to try calling this API manually with an HTTPS token? If we can prove that that works on an instance like yours with SAML enabled, then that could unlock supporting this feature.

[molson504x]

@raffertyuy My understanding is that the export API that bbs2gh uses only supports usernames and passwords - so I'm not sure how we'd solve this.

Would you be willing to try calling this API manually with an HTTPS token? If we can prove that that works on an instance like yours with SAML enabled, then that could unlock supporting this feature.

Can confirm, the BBS export endpoint requires either OAuth authentication or basic auth (username/password). BBS API endpoints that support tokens are scoped to the project-level or repo-level (depending on the token), and the export command has to be able to read outside of the project level as part of the metadata that gets export along with writing a file to the server's file system (which is also part of why SFTP credentials are required).