Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7419

audit.log or server.log logging does not show the MBean attributes which are edited by the User

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Obsolete
    • Major
    • TBD EAP 5
    • EAP_EWP 5.1.1
    • JMX
    • None
    • RHEL 5
      Windows 2008

    Description

      When a user makes any attribute changes from jmx-console.....something like "ExitOnShutdown" attribute is changed to "false" or "true" Or increases or decreases the Thread pool size ...these informations are not logged in any of the logs.

      Example Current scenario:
      ====================

      1). When we enable audit.log logging along with the JAVA_OPTS "-Dorg.jboss.security.web.audit=headers,cookies,parameters" to get the maximum logging informations in the log files.

      2). After logging logs into the "jmx-console" and makes some MBean attribute changes like :
      "jboss.system" ---> "type=ServerConfig" ---> "ExitOnShutdown = False(radio button)

      3). After making the above changes inside the "audit.log" file we see the following kind of informations:
      =========
      2011-10-20 10:54:16,274 TRACE [org.jboss.security.audit.providers.LogAuditProvider] (http-127.0.0.1-8080-3 [Success]Source=org.jboss.security.plugins.javaee.WebAuthorizationHelper;resourcePermissionCheck=true;Exception:=;securityConstraints=SecurityConstraint[HtmlAdaptor];Resource:=[org.jboss.security.authorization.resources.WebResource:contextMap=

      {resourcePermissionCheck=true, securityConstraints=[Lorg.apache.catalina.deploy.SecurityConstraint;@51ab7891, policyRegistration=org.jboss.security.plugins.JBossPolicyRegistration@27e47715}

      ,canonicalRequestURI=/HtmlAdaptor,request=[/jmx-console:cookies=[javax.servlet.http.Cookie@5078a17a]:headers=host=localhost:8080,connection=keep-alive,referer=http://localhost:8080/jmx-console/HtmlAdaptor,content-length=193,cache-control=max-age=0,authorization=origin=http://localhost:8080,user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30,content-type=application/x-www-form-urlencoded,accept=text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8,accept-encoding=gzip,deflate,sdch,accept-language=en-US,en;q=0.8,accept-charset=ISO-8859-1,utf-8;q=0.7,*;q=0.3,cookie=JSESSIONID=C302573FDAE38F2F7E6DDDE7BE1C0160,][parameters=updateAttributes::,jboss.system%3Atype%3DServerConfig::,True::,False::,jboss-service.xml::,False::,],CodeSource=null];policyRegistration=org.jboss.security.plugins.JBossPolicyRegistration@27e47715;
      =========

      [parameters=updateAttributes::,jboss.system%3Atype%3DServerConfig::,True::,False::,jboss-service.xml::,False::,]

      Above log says that "updateAttributes" happened and the current values are True or false..... So currently we don;t display the Attribute name which is actually changed by the user. So it should also display the Attribute Name And their current/changed values which is changed by the logged in user rather than just dumping all the attribute values related to that MBean.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jaysensharma Jay SenSharma (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: