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
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've already added this on the server.xml file but still showing the same result
scheme="https" proxyName="<subdomain.domain.com>" proxyPort="<proxy_port>" secure="true"
I have been trying to follow this tutorial : https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/jiramicrosoft-tutorial
Hi, welcome to the Community!
Jira Server must be available over HTTPS for any SAML configuration to work. That portion of the Azure AD document is designed to get Jira serving over HTTPS.
One thing the Microsoft walkthrough doesn't mention is that you need to restart Jira in order for any changes in server.xml to take effect. If you restart Jira and still have the same trouble, could you post the contents of your server.xml file here (remove the proxy name if you wish) to help troubleshoot?
Thanks!
Daniel | Atlassian Team
I've already done that on my part restarted multiple times but no luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm encountering the same issue. The URLs provided by the plugin are un-editable and defaulting to "http" as opposed to "https". Was a resolution to this ever found?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.