Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,127
Community Members
 
Community Events
176
Community Groups

StartTLS with Crowd

I'm looking for basic instructions to use StartTLS with Crowd directory and an active directory server currently using ldap.  I've enabled StartTLS in the admin area and even though I am able to sync and pull users I get a ton of tls errors in the logs and some users are not getting authenticated.   All is good if I don't use TLS. Do I need to install a cert on the Crowd server for it to use StartTLS?  We don't want to control users in AD from Crowd, just a one way pull.

If we run this command from the Crowd Linux Console:
sudo openssl s_client -connect ADserver.com:636

We do get a valid certificate from the AD server.

Here are some documents I've found but I'm not exactly sure what is needed in our case.

https://confluence.atlassian.com/crowd/troubleshooting-ssl-certificates-and-crowd-164495772.html

https://confluence.atlassian.com/crowd/configuring-an-ssl-certificate-for-microsoft-active-directory-63504388.html

1 answer

1 accepted

0 votes
Answer accepted

Just an update,  I was able to add our wildcard cert which has allowed ldaps to work.  

If I run java SSLPoke adserver.com 3269 it works connects. but if I change it to port 389 for tls it doesn't work:

java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:209)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
at sun.security.ssl.InputRecord.read(InputRecord.java:503)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:747)
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:138)
at SSLPoke.main(SSLPoke.java:23)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
3.5
TAGS

Atlassian Community Events