Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-4462

[Java Broker] SimpleLDAPAuthenticationManager does not register SASL mechanism PLAIN

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.18, 0.19, 0.20, 0.21
    • 0.22
    • Broker-J

    Description

      If the user tries to configure only the simple-ldap-auth-manager, client see the following exception on attempting to connect.

      javax.jms.JMSException: Error creating connection: Error: Unable to create SASL Server:PLAIN
      	at org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:125)
      	at org.apache.qpid.example.Hello.runTest(Hello.java:51)
      	at org.apache.qpid.example.Hello.main(Hello.java:40)
      

      The issue is that SimpleLDAPAuthenticationManager is omitting to register the PLAIN SASL mechanism.

      The user can workaround the issue by configuring a plain pd-auth-manager, (which causes the SASL mechanism to be registered) and specifying a default-auth-manager of SimpleLDAPAuthenticationManager as illustrated below:

      <default-auth-manager>SimpleLDAPAuthenticationManager</default-auth-manager>
      <pd-auth-manager>
        <principal-database>  <class&gt;org.apache.qpid.server.security.auth.database.PlainPasswordFilePrincipalDatabase</class&gt;
          <attributes>
             <attribute>
               <name>passwordFile</name>
               <value>${conf}/emptypasswd</value>
             </attribute>
          </attributes>
        </principal-database>
      </pd-auth-manager>
      
      

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            robbie Robbie Gemmell
            kwall Keith Wall
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment