Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-62615

JIRA features that require password confirmation (websudo, captcha) do not work with custom authentication

    XMLWordPrintable

Details

    • 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.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Confluence has had the ability to use websudo with a custom authenticator since 3.5, using password.confirmation.disabled flag (see CONF-20958).

      Why s there no such capability with JIRA?

      Doing something similar to isPasswordConfirmationDisabled() in com.atlassian.jira.security.websudo.InbuiltAuthenticatorCheck would bring some commonality between Confluence and JIRA.

      Why? I have implemented custom authenticators for JIRA and Confluence - based on MIDANAuthenticator - whilst waiting for a solution to JSD-1244. (Accepting that internal users with a Crowd account get SSO features but external JSD customers don't)

      With a custom authenticator I can still have websudo in Confluence; but not with JIRA.

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-62615 JIRA features that require password confirmation (websudo, captcha) do not work with custom authentication

          • Closed

          Activity

            People

              Unassigned Unassigned
              d9d8b2bae4ab Mark Bewley
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: