Authentication failed when invoking jolokia URL management api with AMQ on OpenShift

Solution Verified - Updated -

Issue

  • Authentication failed when invoking jolokia URL management api to monitor broker with AMQ on OpenShift:
user@testmachine:~/apps$ curl -k --user admin:admin https://openshift.example.com:443/api/v1/namespaces/testproject/pods/https:jboss-amq-63-2-56dlg:8778/proxy/jolokia/read/org.apache.activemq:type=Broker,brokerName=jboss-amq-63-2-56dlg,destinationType=Queue,destinationName=test/QueueSize
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "pods \"https:jboss-amq-63-2-56dlg:8778\" is forbidden: User \"system:anonymous\" cannot get pods/proxy in the namespace \"testproject\": proxy subresource changed to unsafeproxy\nno RBAC policy matched, proxy subresource changed to unsafeproxy",
  "reason": "Forbidden",
  "details": {
    "name": "https:jboss-amq-63-2-56dlg:8778",
    "kind": "pods"
  },
  "code": 403

Environment

  • Red Hat JBoss A-MQ 6.x for OpenShift

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content