In bitbucket.properties, we have configured all connections to require SSL, but we actually want to exclude /scm/* path requests from this requirement. (We would prefer not to install a reverse proxy in front of tomcat, if we can avoid it.)
Is there any way to do this?
This is to accommodate the hundreds of legacy Git remote URLs we have, that would need to be updated. We don't consider this much of a security risk, since all access is inside the corporate network, and the repos being cloned are sitting, unencrypted, on the network, anyway.
But we do want to enforce HTTPS connections in the web UI, to prevent passwords from being sent in the clear.
Here is the relevant part of our bibtucket.properties file:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs