Open issues

Order by Priority
  1. Suggestion
    ACCESS-1277Allow domains to be added to the IP Allowlist
  2. Suggestion
    ACCESS-1317Need a way to handle Shadow IT after domain claim
  3. Suggestion
    ACCESS-1552Allow org admin to unlink social login (Auth0)
  4. Suggestion
    ACCESS-1853Provide option to show the site deletion workflow status and associated date in the Org admin page.
  5. Suggestion
    ACCESS-1872Provide option to expedite deletion of shadow sites
  6. Suggestion
    ACCESS-2198Email notification before SCIM API key expiry
  7. Suggestion
    ACCESS-2213Organization Insights: Provide example use cases to org. admins for the use of Insights
  8. Suggestion
    ACCESS-1148Improve the administration interface for User Provisioning
  9. Suggestion
    ACCESS-1260Additional events and information on user activity logs for Confluence
  10. Suggestion
    ACCESS-1196Add details on the admin API key to org audit logs
  11. Suggestion
    ACCESS-1296Confluence attachment events on org audit log
  12. Suggestion
    ACCESS-1009Ability to control site/organization access for accounts via user provisioning
  13. Suggestion
    ACCESS-1334View/Control User's access to Bitbucket
  14. Suggestion
    ACCESS-1257Additional options to receive MFA code
  15. Suggestion
    ACCESS-1444Allow Org Admin to receive email notification before SAML certificate expiry
  16. Suggestion
    ACCESS-1606Jira user properties API
  17. Suggestion
    ACCESS-1737Re-sync a provisioned external account with the Provisioned data following email address change
  18. Suggestion
    ACCESS-914Allow Customers to Customize the Given/SurName SAML Attributes in Okta App
  19. Suggestion
    ACCESS-1294Update the Okta cloud application to make Jira/Confluence/etc chiclets configurable per user or group
  20. Suggestion
    ACCESS-2137Ability to track unmanaged accounts login/logout activities in the Org level Audit logs
  21. Suggestion
    ACCESS-2207Support custom mapping for display name when Azure AD sync is enabled
  22. Suggestion
    ACCESS-2208IP allowlisting should indicate soft deletion site error
  23. Suggestion
    ACCESS-2210Provide a Detailed Access Denied Message for Org Admins Attempting to Access Personal Bitbucket Workspaces
  24. Suggestion
    ACCESS-1714Allow IP Allowlisting for admin.atlassian.com pages
  25. Suggestion
    ACCESS-1421Improve organization audit log for IP allowlisting
  26. Suggestion
    ACCESS-1802IP allowlist should send notification to all admins when enabled/edited/disabled
  27. Suggestion
    ACCESS-1323A search function to narrow down the IP allowlists that had been applied to a certain sites
  28. Suggestion
    ACCESS-2179Provide sorting/filtering capabilities to the IP Allowlist page
  29. Suggestion
    ACCESS-2196Provide different MFA options such as TrustBuilder
  30. Suggestion
    ACCESS-1529Ability to export data from Insights
  31. Suggestion
    ACCESS-1688Provide self-serve functionality for OrgAdmin to unlink Bitbucket workspace from Atlassian organization
  32. Suggestion
    ACCESS-2177Revoke API Token Automatically When the Token has Expired
  33. Suggestion
    ACCESS-2194Email and in-product notifications when SCIM API key is close to expiration
  34. Suggestion
    ACCESS-2205Customization of 2FA Notification Emails
  35. Suggestion
    ACCESS-1572Allow unmapped/empty fields to be editable by admins or user for IDP synced accounts
  36. Suggestion
    ACCESS-1654Include audit logs for JWM/Business type projects
  37. Suggestion
    ACCESS-2058Ability to allow Org Admin to be able to configure their notification base on schedules
  38. Suggestion
    ACCESS-2204Shadow IT - Unable to approve products to be created outside the organization
  39. Suggestion
    ACCESS-1825External Users || Enforce MFA || Authenticator apps
  40. Suggestion
    ACCESS-621Ability to provision users to Bitbucket Cloud repositories with SCIM
  41. Suggestion
    ACCESS-2202Customization for Guard Premium's Data Classification Field in Jira
  42. Suggestion
    ACCESS-571Allow Organization admins to manage individual application access.
  43. Suggestion
    ACCESS-1315Include support ticket information for Atlassian Support IP Policy in Security > IP allowlisting
  44. Suggestion
    ACCESS-1578SAML SSO email changes don't appear on organization Audit Logs
  45. Suggestion
    ACCESS-1653Organization audit logs should show users being added to default groups when first invited to a site
  46. Suggestion
    ACCESS-2200Customer SSO redirect ignores the redirect request
  47. Suggestion
    ACCESS-2156Ability to set up a security notification to all Org admins about any new Administrative access role is granted to a new user
  48. Suggestion
    ACCESS-1010Improve SSO enabled user login error messaging
  49. Suggestion
    ACCESS-1423Export Organization Users using API is missing "added to org" field.
  50. Suggestion
    ACCESS-1763[Tracking in Issue Links] Organisation-level audit log feature requests
Refresh results
153 of 729
Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1552

Allow org admin to unlink social login (Auth0)

    • 15

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem

      Today if a user logging in using social login(Continue with Microsoft/Google/Apple) it will link to their Atlassian account and require the user to login via that social method in the future. But, if this user wants to back to using local Atlassian credentials to log in (email/password), like if the email address is no longer managed by that authenticator, is not option for the user or for the org admin to unlink it.

      Workaround

      At the moment the customer can contact support and request to have their Atlassian account unlinked from their social account.

            There are no comments yet on this issue.

              Unassigned Unassigned
              e7daa085fa6d Jose da Silva
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: