Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-25384

Error Testing LDAP Authentication: Write operations are not allowed in read-only mode (FlushMode.NEVER):

XMLWordPrintable

      When connecting MS LDAP server with settings that work fine with JIRA 5 I get the following error.

      Test user can authenticate : Failed
      Write operations are not allowed in read-only mode (FlushMode.NEVER): Turn your Session into FlushMode.AUTO or remove 'readOnly' marker from transaction definition.

      Steps to reproduce

      1. Set up LDAP directory in Confluence Admin
      2. Enter a user and test their authentication
      3. Error message will appear
      4. Synchronise the directory and note that the user is created
      5. Log in as the user, this will be successful

      Resolution

      This error message occurs despite the authentication test being successful. It does not indicate an actual error in authentication, and no functionality is affected. You can safely continue to configure the LDAP directory and it will be successful.

        1. CONF-25384.png
          48 kB
          Denise Unterwurzacher [Atlassian]

            [CONFSERVER-25384] Error Testing LDAP Authentication: Write operations are not allowed in read-only mode (FlushMode.NEVER):

            Deleted Account (Inactive) added a comment -

            Ignore previous comment as not relevant to CSP-95157.

            Deleted Account (Inactive) added a comment - Ignore previous comment as not relevant to CSP-95157.

            Deleted Account (Inactive) added a comment -

            It looks like this was fixed in 4.3.7. Is it correct to assume that this is still a problem in 4.3.3, and that there is a patch we can apply to 4.3.3? We may need this as an URGENT need for our Sev1 ticket CSP-95157.

            Deleted Account (Inactive) added a comment - It looks like this was fixed in 4.3.7. Is it correct to assume that this is still a problem in 4.3.3, and that there is a patch we can apply to 4.3.3? We may need this as an URGENT need for our Sev1 ticket CSP-95157.

            David Rizzuto added a comment - - edited

            I tracked down the problem - the embedded crowd admin plugin does these tests. The final authentication test actually writes back to the database, updating the 'lastAuthenticated' and 'invalidAuthenticationAttempts' fields. However there action were not done in a transaction, so failed. Wrapping it in a transaction interceptor did the trick.

            David Rizzuto added a comment - - edited I tracked down the problem - the embedded crowd admin plugin does these tests. The final authentication test actually writes back to the database, updating the 'lastAuthenticated' and 'invalidAuthenticationAttempts' fields. However there action were not done in a transaction, so failed. Wrapping it in a transaction interceptor did the trick.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment -
            Steps to reproduce
            1. Set up LDAP directory in Confluence Admin
            2. Enter a user and test their authentication
            3. Error message will appear
            4. Synchronise the directory and note that the user is created
            5. Log in as the user, this will be successful

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - Steps to reproduce Set up LDAP directory in Confluence Admin Enter a user and test their authentication Error message will appear Synchronise the directory and note that the user is created Log in as the user, this will be successful

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment -

            Hi Rob,

            Thanks for reporting this. We've been able to reproduce it, but what we've found is that the error isn't correct, it simply shows regardless of the result of the authentication test. If you attempt to log in to Confluence as the LDAP user it is successful. I'd recommend trying to log in as the user you used for the test, and if you're still having trouble, raise a ticket in our support system so we can help you troubleshoot it.

            This issue will be used to track work on that particular bug now. If you need any help with setting up the LDAP just raise a ticket in support.atlassian.com.

            Kind regards,
            Denise
            Atlassian Support - Sydney

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - Hi Rob, Thanks for reporting this. We've been able to reproduce it, but what we've found is that the error isn't correct, it simply shows regardless of the result of the authentication test. If you attempt to log in to Confluence as the LDAP user it is successful. I'd recommend trying to log in as the user you used for the test, and if you're still having trouble, raise a ticket in our support system so we can help you troubleshoot it. This issue will be used to track work on that particular bug now. If you need any help with setting up the LDAP just raise a ticket in support.atlassian.com. Kind regards, Denise Atlassian Support - Sydney

              drizzuto David Rizzuto
              aaecbe3fe711 rob nield
              Affected customers:
              4 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: