Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-62615

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

          relates to

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

          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: