Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9343

Legacy ldap realm returns 401 if LDAP is unreachable

XMLWordPrintable

    • Hide

      1) Start server

      ./standalone.sh
      

      2) Configure server with CLI

      /core-service=management/ldap-connection=ldapConnection:add(url="ldap://localhost:10389", search-credential="secret", search-dn="uid=admin,ou=system")
      /core-service=management/security-realm=ldap-realm:add()
      /core-service=management/security-realm=ldap-realm/authentication=ldap:add(connection=ldapConnection, base-dn="ou=People,dc=jboss,dc=org", username-attribute=uid)
      /core-service=management/management-interface=http-interface:write-attribute(name=security-realm, value=ldap-realm)
      reload
      

      3) Access http://localhost:9990/management?operation=attribute&name=server-state in browser and provide credentials
      4) Instead of 401 status code 500 is returned

      Show
      1) Start server ./standalone.sh 2) Configure server with CLI /core-service=management/ldap-connection=ldapConnection:add(url= "ldap: //localhost:10389" , search-credential= "secret" , search-dn= "uid=admin,ou=system" ) /core-service=management/security-realm=ldap-realm:add() /core-service=management/security-realm=ldap-realm/authentication=ldap:add(connection=ldapConnection, base-dn= "ou=People,dc=jboss,dc=org" , username-attribute=uid) /core-service=management/management- interface =http- interface :write-attribute(name=security-realm, value=ldap-realm) reload 3) Access http://localhost:9990/management?operation=attribute&name=server-state in browser and provide credentials 4) Instead of 401 status code 500 is returned

      • In EAP 7.0 legacy ldap realm returns 401 if LDAP server is unreachable.
      • In EAP 7.1 it changed to 500. QE and Dev aggreed it is more accure and documentation JIRA was created to cover this change JBEAP-8125 .
      • Now again in DR13 legacy ldap realm returns 401 if LDAP server is unreachable

      Based on prior Dev/QE agreement and current contradiction to documentation, I consider this to be a bug.

              darran.lofthouse@redhat.com Darran Lofthouse
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: