Connecting through secure LDAP from BitBucket Server to Azure AD Domain Services results in intermittent Timeout errors.
Here are the error messages that are in the atlassian-bitbucket.log:
org.springframework.ldap.ServiceUnavailableException: ldap.mydomain.com:636; socket closed; nested exception is javax.naming.ServiceUnavailableException: ldap.mydomain.com:636; socket closed; remaining name 'ou=AADDC Users,DC=mydomain,DC=com'
Reviewing the network capture we can see that the connection is established without problems between the Azure AD Domain Services secure LDAP and the BitBucket Server, but after some time the client server sends an Encrypted Alert which causes the Azure AD Domain Services to close the connection. I think this may be a bug?
Hi Brendan, we'd need to know if this is coming from Azure or Bitbucket; "the client server sends an Encrypted Alert" is ambiguous. Since the packets are encrypted, we can't be sure if it's an orderly shutdown or a termination due to an encryption problem, probably from the symmetric key exchange. If the packet is coming from Azure, we would need the Azure logs
There are two possibilities here:
Most of what seems to be happening here is below our app. It's either Java or the system making this negotiation, we haven't found any other reports of this to Atlassian.
Let us know!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot