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

I want to automatically login to Confluence with a fixed user/password? So not using SSO and not using anonymous.

Currently we are developing a cloud application. We would like to use Confluence Cloud for creating help pages for our own cloud application. We would like to create 2 spaces in Confluence. 1 space with internal documentation, user login is required for this space. The other space will contain the help text for our cloud application. Users that are logged on to our cloud application need read only access to this help space and are allowed to see everything in this space. But we do not want our help pages to be visible publicly from the internet. We do not want the users from our cloud application to have to login to be able to view the help text. But if we use anonymous login, then the space is visible to the world, which we do not want. Is it possible to create a generic help_user with read access to the entire Help space, and use a simple API to automatically login to confluence from our cloud application? A SSO solution is to complex. We do not want to have to setup a new user on confluence, every time our customers add a new user in our cloud application.

4 answers

0 votes
Dario B
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 13, 2017

You can try to use Oauth as explained in below tutorial:

Otherwise you can also use basic authentication or Cookie authentication (but this last one is at the moment affected by a bug tracked in: in this case you can use basic auth, intercept the cookie and then use it to authenticate the subsequent requests):


Best Regards,
Atlassian Cloud Support

How can i use the cookie from the basic authentication to authenticate the future requests?

here is the response i received in my back end from confluence

 curl -D- -u test:test123 -X GET -H "Content-Type: application/json"
HTTP/1.1 404
X-ASEN: SEN-L12887861
Set-Cookie: JSESSIONID=E93E362BD9F2CEA1922ABA486D130BAD; Path=/; HttpOnly
X-Seraph-LoginReason: OK
Cache-Control: no-transform
X-Content-Type-Options: nosniff
Vary: Accept
Content-Type: application/xml
Content-Length: 186
Date: Fri, 04 Jan 2019 17:55:51 GMT


How can i use this cookie to authenticate and launch a confluence url accessible to the user "test"?


Dario B
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 31, 2019

Hi @Dario B 

the instructions has been deprecated, other options?


@Karin Heijboer did you solve your issue?
I have the same need

I have the exact same problem, we used to pass the username and password as part of the URL (not ideal I know) but now that method of authentication has been forbidden by Atlassian. What's the alternative?

0 votes
Robert Massaioli (Atlassian)
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 05, 2017

Have you considered using Atlassian Connect to build a tight integration and solve this problem: ?

0 votes
Rodney Hughes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 02, 2017

your generic help_user will not help them - then they have to sign on either as themselves or as the help_user and then the generic help_user effectively becomes anonymous access as there is no prevention of the User remembering their log in after they leave your client's company, or posting it on facebook or wiki-leaks ...

Making sure each User has their own account ensures you have control over revoking their access when needed and gives them a sense of "confidentiality" and the "prestige" of being a trusted person - it is worth it!

The simple answer is grant your Users access to the two Spaces on the Cloud instance - they would only have view access to pages in the "Help Space".

One way of doing that is giving the Help Space access to the group "All Confluence Users" so every new User automatically is included in that group.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events