Error: “RoleBasedAuth E SECJ0306E: No received or invocation credential exist on the thread. The Role based authorization check …”

When using the Diagnostics 8.04 Java Agent to probe a WebSphere 6.1 Application Server (WAS), if the following error messages are repeatedly written to the WAS SystemOut.log:

[3/19/11 18:35:09:625 CET] 00000028 RoleBasedAuth E SECJ0306E: No received or invocation credential exist on the thread. The Role based authorization check will not have an accessId of the caller to check. The parameters are: access check method getState on resource Server and module Server. The stack trace is java.lang.Exception: Invocation and received credentials are both null

at com.ibm.ws.security.role.RoleBasedAuthorizerImpl.checkAccess(RoleBasedAuthorizerImpl.java:287)

at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2061)

at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:1900)

at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:1800)

at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:1773)

at com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminServiceImpl.java:735)

at com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminServiceImpl.java:702)

at com.ibm.ws.management.PlatformMBeanServer.getAttribute(PlatformMBeanServer.java:662)

at com.mercury.diagnostics.capture.metrics.jmx.WebSphereJMXCollector.isStartupCompleted(WebSphereJMXCollector.java:158)

at com.mercury.diagnostics.capture.metrics.jmx.WebSphereJMXCollector.doInitialize(WebSphereJMXCollector.java:65)

at com.mercury.diagnostics.capture.metrics.jmx.JMXCollector.initialize(JMXCollector.java:139)

at com.mercury.diagnostics.capture.metrics.CollectorControl.initialize(CollectorControl.java:385)

at com.mercury.diagnostics.capture.metrics.CollectorAgent.validateInitialization(CollectorAgent.java:912)

at com.mercury.diagnostics.capture.metrics.CollectorAgent.run(CollectorAgent.java:681)

at java.lang.Thread.run(Thread.java:810)

.

[3/19/11 18:35:09:633 CET] 00000028 RoleBasedAuth A SECJ0305I: The role-based authorization check failed for admin-authz operation Server:getState. The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: adminsecuritymanager, operator, iscadmins, deployer, administrator, monitor, configurator.

[3/19/11 18:35:09:695 CET] 00000028 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /prod/IBM/websphere61/AppServer/profiles/mpeprodmpeasp06/logs/ffdc/ap1ga0f1_00000028_11.03.19_18.35.09_0.txt

[3/19/11 18:35:09:711 CET] 00000028 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /prod/IBM/websphere61/AppServer/profiles/mpeprodmpeasp06/logs/ffdc/ap1ga0f1_00000028_11.03.19_18.35.09_0.txt

[3/19/11 18:35:09:771 CET] 00000028 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file /prod/IBM/websphere61/AppServer/profiles/mpeprodmpeasp06/logs/ffdc/ap1ga0f1_00000028_11.03.19_18.35.09_1.txt

[3/19/11 18:35:09:787 CET] 00000028 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file /prod/IBM/websphere61/AppServer/profiles/mpeprodmpeasp06/logs/ffdc/ap1ga0f1_00000028_11.03.19_18.35.09_1.txt

WebSphere 6.1 uses role-based security to protect access to the MBeanServer when administrative security is ‘on’. This causes security exceptions when the Diagnostics JMX collectors access the MBeanServer. A workaround for this issue is included in the Diagnostics WebSphere6JMXCollector. However, when the Diagnostics Java Agent runs with WAS 6.1, both the Diagnostics WebSphere5JMXCollector and WebSphere6JMXCollector find the same WAS MBeanServer instance. The errors are reported as the WebSphere5JMXCollector does not include the required workaround.

To remove this error, modify the file "metrics.config" in the probe configuration "/etc" directory and either comment out or remove the metrics entries for the WebSphere V5.x Collector, that is, comment/delete all entries beginning with "WebSphere5" for instance:

WebSphere5/beanModule.creates = EJB Creates|count|EJB

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s