-
Suggestion
-
Resolution: Fixed
-
None
Hi,
We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature (https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket (https://support.atlassian.com/contact/#/) and we will enable the feature for you.
Thanks,
The Atlassian Access team.
Problem definition
Currently when a domain is verified Atlassian accounts become managed accounts for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across ALL Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello.
- Further details and clarifications are available here: Atlassian Access for Cloud FAQs
Suggested resolution
Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts.
- is duplicated by
-
ACCESS-141 Trello charges on Atlassian Access
- Closed
- is related to
-
ACCESS-764 Selective user claim
- Closed
-
ACCESS-88 Ability to Apply Security Policies for Individual Managed Accounts
- Closed
-
ACCESS-665 Allow enforcing 2FA on a sub-set of domain users
- Closed
- relates to
-
ACCESS-37 Have the option to configure SAML at instance level rather than at organization level
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[ACCESS-605] Allow Atlassian Access security policies to a subset of the managed accounts in an organization
Remote Link | New: This issue links to "Page (Confluence)" [ 552763 ] |
Description |
Original:
{panel:title=May 2021 Update}
Hi, We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature ([https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies]). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket ([https://support.atlassian.com/contact/#/]) and we will enable the feature for you. Thanks, The Atlassian Access team. {panel} h3. Problem definition Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello. * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access] h3. Suggested resolution Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts. |
New:
{panel:title=May 2021 Release Update}
Hi, We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature ([https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies]). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket ([https://support.atlassian.com/contact/#/]) and we will enable the feature for you. Thanks, The Atlassian Access team. {panel} h3. Problem definition Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello. * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access] h3. Suggested resolution Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts. |
Description |
Original:
{panel:title=January 2021 Update}
Hi Everyone, We are actively working to ship this solution. Our current ETA is end of April 2021. We will update this issue as soon as we make the solution generally available. Thank you, The Atlassian Access team {panel} h3. Problem definition Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello. * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access] h3. Suggested resolution Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts. |
New:
{panel:title=May 2021 Update}
Hi, We are excited to announce that we have shipped the Authentication policies feature. You can now apply Atlassian Access security policies on a subset of managed accounts using this feature ([https://www.atlassian.com/software/access/guide/elements/authentication-policies#why-apply-multiple-authentication-policies]). We are still in the last leg of the rollout. If your organization doesn’t have the feature yet, file a support ticket ([https://support.atlassian.com/contact/#/]) and we will enable the feature for you. Thanks, The Atlassian Access team. {panel} h3. Problem definition Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello. * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access] h3. Suggested resolution Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts. |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 548591 ] |
Description |
Original:
{panel:title=January 2021 Update} Hi Everyone, We are actively working to ship this solution. Our current ETA is April 2021. We will update this issue as soon as we make the solution generally available. Thank you, The Atlassian Access team {panel} h3. Problem definition Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello. * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access] h3. Suggested resolution Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts. |
New:
{panel:title=January 2021 Update}
Hi Everyone, We are actively working to ship this solution. Our current ETA is end of April 2021. We will update this issue as soon as we make the solution generally available. Thank you, The Atlassian Access team {panel} h3. Problem definition Currently when a domain is verified Atlassian accounts become _managed accounts_ for all users using emails under the claimed domain. If an Atlassian Access feature such as SAML SSO or two-step verification is enabled/enforced it will impact all managed accounts across *ALL* Atlassian Access supported products such as Jira Software, Jira Service Desk (agents), Jira Core, Confluence, Bitbucket, Opsgenie, or Trello. * Further details and clarifications are available here: [Atlassian Access for Cloud FAQs|https://www.atlassian.com/licensing/atlassian-access] h3. Suggested resolution Org administrators must be able to apply Atlassian Access security features to a subset of the managed accounts in the organization and only pay for these accounts. |
Remote Link | New: This issue links to "Page (Confluence)" [ 534277 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 527681 ] |
Link |
New:
This issue is duplicated by |