Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

SSL connection to Crowd doesn't work on SuSe with TOMCAT HTTPS Config

SSL connection to Crowd doesn't work on SuSe with TOMCAT HTTPS Config

After following the instructions and trying this:

<Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
           maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
           clientAuth="false" sslProtocol="TLS"
           keystoreFile="${user.home}/.keystore" keystorePass="changeit"
           keyAlias="tomcat" keyPass="changeit"/> 

This simply doesn't work according to the instructions on the Atlassian website. I do not even get any error message. I tried this on SuSe Linux. It just hangs and times out without even an error message. I tried the following:

* curl --noproxy "*" https://localhost:8443 -v

* wget --no-proxy https://localhost:8443

*  openssl s_client -connect https://127.0.0.1:8443

* Adding the 8443 port to the SuSe firewall and reloading the firewall

* Changing the above to 443 instead of 8443

* Reading the Atlassian Crowd logs (nothing useful therein)

* Reading the Tomcat Apache Cataline logs (nothing useful therein except useless timeout message)

* Praying...

 

It does however work with an nginx reverse proxy bolted on at the front. I guess that rules out firewall issues then :-)

With the Atlassian/Tomcat method of enabling HTTPS, it doesn't even give any error. It just sits there for ages then times out.

?

 

1 answer

0 votes
Marcin Kempa Atlassian Team Feb 26, 2018

Hi @N B,

 

Can you check if Tomcat is listening on the port you configured HTTPS?

When you are saying that:

It does however work with an nginx reverse proxy bolted on at the front.

does it mean that https works then with Crowd? or is your nginx doing SSL termination?

Could you post output of curl?

 

Best Regards,

Marcin Kempa

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

181 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you