Skip to content
This repository has been archived by the owner on Jan 19, 2019. It is now read-only.

Customization of 'activemq' admin console from 'out of box' default setup #20

Open
bharghav9 opened this issue Jul 15, 2014 · 0 comments

Comments

@bharghav9
Copy link

Version:

Activemq[1.3.3]
https://github.com/opscode-cookbooks/activemq

Environment:

CentOS 6.3
activemq[cookbook]

Scenario:

Customization of 'activemq' console. "Out of box" installation for production application is the top "security vulnerability". So in order to avoid this, I had customized current 'activemq' to allow customization related to 'activemq' admin console.

Steps to Reproduce:

This is not an issue, just a small enhancement to existing to 'activemq' cookbook.

Expected Result:

Once below commits are merged

  1. bharghav9/activemq@a9ce1d4
  2. bharghav9/activemq@d75901d

the admin console configuration can defined using following attributes.

Admin console properties

default['activemq']['admin_console']['customize'] = 'false'
default['activemq']['admin_console']['port'] = '9161'
default['activemq']['admin_console']['credentials']['customize'] = 'true'
default['activemq']['admin_console']['credentials']['user_name'] = 'admin'
default['activemq']['admin_console']['credentials']['password'] = 'admin'
default['activemq']['admin_console']['new_admin_console_name'] = 'admin'

Actual Result:

Once above commits are merged, the 'admin' console is accessible over '9161'(any port provided at runtime) and the context name defined by 'new_admin_console_name'. So the activemq admin console will be accessible on 'http://:/. Also the user can't login using default credentials, they can login with values provided for 'user_name','password'.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants