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,559,159
Community Members
 
Community Events
184
Community Groups

How can I change the http to https in the identifier.

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

1 answer

0 votes
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 01, 2020

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

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?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events