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

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


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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What is the right way to create the Crowd SSO cookie in custom .Net application


I am trying to create a Crowd client for a custom .Net application.  And from other questions on this forum I understand that I need to create a cookie for the token returned by SSO Authentication Crowd REST API.  And that I need to submit ValidationFactors with these 2 specific items: "remote_address" and "X-Forwarded-For".  I found this information in this post:

My code creates the SSO cookie accordingly.  However, JIRA and Confluence do not recognize the cookie created by my custom .net application; but they recognize each other's cookies.  So after logging in on the custom application, I would have to again login to JIRA.

Has anyone accomplished this in the recent versions of Crowd?  Any ideas please?

Rizwan Basha

1 answer

HI, I have a similar issue. 

My application : SSL and authenticates to crowd. (No problem)

Confluence : uses actual port 8090, but uses url rewrite to run on SSL.  

So, in actual fact both application are on SSL, only that confluence uses ARR or url rewrite. When I access via https to confluence , it does not work, but if access via port 8090, it works. e.g https://knowledge.example,com will not work, will work. After accessing via 8090, will log on.


I have few other issue before maybe you  should check following as well:

1. If your custom application is on a load balancer, you will use X-forward-for to get client ip, if you have no load balancer, you will only use remote_addr.

2. The other thing, you can try direct access via the confluence port 8090, instead of through a url rewrite. 

I am still trying to figure out why url rewrite does not work.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events