On this page:
| Table of Contents | ||
|---|---|---|
|
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.
...
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 the table 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.
...
Your app(s)
...
...
...
Confluence
...
Refined Sites for Jira Service Management
...
Jira
...
Both Refined Sites for Confluence and Refined Sites for Jira Service Management
...
Jira, also if a site doesn’t contain Jira content. In the future it’ll be possible decide per site whether users authenticate with Jira or Confluence. Read about upcoming features in our roadmap.
| Info |
|---|
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 against with Atlassian is necessary to get Atlassian data onto the sites. |
Control over login route
...
| Info |
|---|
This setting is only visible to customers who use both Refined for Confluence and Refined for Jira Service Management. |
Set up whether users log in to your site through either Confluence or Jira authentication. By default, the login route is set to Jira. The best route for users to log in depends on your site’s contents:
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 prompted to request access to Jira.
In the same vein, choose Jira as the login route if your site contains only Jira or Jira Service Management content.
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
...
Hide the login button (see steps above).
Create or go to the page that will serve as a login page.
Open the Page Builder.
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.
...