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.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
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!
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.
1 answer
Hi @Nayan Gupta
If talking about the SSL certificate, then Crowd doesn't directly integrate with it. Only Apache Tomcat holds all required configurations for support SSL.
I checked the proposed configuration (official Atlassian Crowd documentation) with the Self-Signed certificate and with a certificate issued by CA (https://letsencrypt.org). In both cases, everything works as it should, but the Connector configuration for a certificate issued by Let's Encrypt is a little bit changed (see below).
So, if you are sure that it is all configured correctly, then I recommend trying to find the root cause of the problem on the client-side and maybe some recommendations provided in this article help you https://geeksadvice.com/fix-net-err-cert-date-invalid-error
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.