Logging in and out
- Madzy Soetman
- Raj Sehmi
On this page:
When do users need to log in
Some content on a Refined site is only visible for users who are logged in:
On private or support sites, users always have to log in.
On public sites, users have to log in to see:
Landing pages of Jira Service Management projects.
Request types in Request Types modules and My Requests modules.
Issues in Issue Types modules and Jira Issues modules.
Refined Pages, links and menu folders that are set to be visible to logged-in users only.
Sections and rows on a page that are set to be visible to logged-in users only.
On public sites, users can use the login button in the navigation menu to log in themselves, or they are prompted to log in when they try to access a restricted page.
Authentication
Upon logging in on a Refined site, users are directed to Atlassian. Here they log in with their Atlassian account through either Confluence or Jira (see “Control over login route” below). Once they’ve logged in, they’re directed back to the Refined site. Users stay logged in for seven days, unless they log out themselves.
Because Refined sites direct users to Atlassian to log in, we don’t support Single Sign On (SSO) integrations from providers such as Okta or Azure Active Directory. Authenticating with Atlassian is necessary to get Atlassian data onto the sites.
Control over login route
When the site contains content from only Refined for Confluence or Refined for Jira Service Management, the users log in through that specific Atlassian tool. When the site contains content from both apps, you can choose which tool is used for login purposes. By default, the login route is set to Jira if you have both Refined Sites apps.
The best route for users to log in depends on your site content:
If your site contains content from both Atlassian products, we generally recommend choosing the product that most users have access to.
For example, your organization may have guest users in Confluence, who don’t have access to Jira. Choosing the login route through Confluence makes sure these users won’t have to request Jira access to log in.If your site contains only Confluence content, let users log in through Confluence.
Otherwise, users who have access to Confluence but not Jira are asked to request access to Jira.If your site contains only Jira Service Management content, choose Jira as the login route.
Otherwise, users who have access to JSM but not Confluence are asked to request access to Confluence.
Is Jira your login route?
When a user logs in to your Refined site, they're directed to log in on the native JSM help center, and then directed back to the Refined site again. So for a smooth experience, we recommend to align the background of the native JSM help center with the looks of the Refined site. Follow this guide to customize the look and feel of the banner.
Choose the login route
Go to the Refined Administration.
Click Sites in the left-hand menu.
Pick a site.
Go to the Permissions tab.
Scroll down to the Login route section.
Select the login route.
"Log out from Atlassian" prompt
After logging out from the site, users are not automatically logged out of Atlassian. For organizations in which multiple employees use the same laptop, tablet, or other device, this may pose complications. To emphasize to users that they also need to log out of Atlassian, enable the Log out from Atlassian prompt.
The prompt differs depending on the type of user:
Licensed users can click a Log out from Atlassian button, which redirects them to the Atlassian log-out page.
JSM customer users are instructed how to log out from the JSM customer portal. Clicking the Continue button takes them to the customer portal in Atlassian. Here they have to log out by clicking their profile icon in the top-right of the screen.
Enable the prompt
Go to the Refined Administration.
Click Sites in the left-hand menu.
Pick the site you want to work with.
Go to the Configuration tab.
Scroll down to the Security heading > turn on ”Log out from Atlassian” prompt.
Hide the login button
While the login button is part of the header by default, you may want to hide it on some types of sites. For example on a public documentation site on which the majority of users will only read information and has no reason to log in.
To hide the login button:
Go to the Refined Administration.
Click Sites in the left-hand menu.
Select a site.
Go to the Configuration tab.
Scroll down to the Header section.
Turn off Login button.
If you were using custom CSS to hide the login button before we released this feature, we recommend you to remove it and use the feature instead. We don’t offer support for issues that occur due to custom code.
Create a dedicated login page
On some sites, you may want to hide the login button from the navigation menu but still offer certain users a way to log in. You can create a dedicated landing page for this:
Hide the login button (see steps above).
Create or go to the landing page that will serve as a login page.
Add the login URL (subdomain).(domain.com)/login to a module: for example a Button module, Image module, or a link in a Text module.
Use view permissions to make the page look different based on whether the user is logged in or not. For example, hide the section or row that contains the module with the login link for users who are already logged in.