THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
No Format |
---|
<security>
<principal-databases>
<principal-database>
<!-- A name for referencing this database-->
<name>passwordfile</name>
<!-- The type of principal database -->
<class>org.apache.qpid.server.security.auth.database.PlainPasswordVhostFilePrincipalDatabase</class>
<!-- Any attributes associated with the database. Here it is a password file to load. -->
<attributes>
<attribute>
<name>passwordFile</name>
<value>${conf}/passwdVhost</value>
</attribute>
</attributes>
</principal-database>
</principal-databases>
<!-- This access value can be any access manager. The built in defaults are AllowAll and DenyAll -->
<access>
<class>org.apache.qpid.server.security.access.AllowAll</class>
</access>
<!-- Properties required when running the JMX Management console. -->
<jmx>
<!-- Access file that allows users rights to access the management console. -->
<access>${conf}/jmxremote.access</access>
<!-- The principal database to use to authenticate users. -->
<principal-database>passwordfile</principal-database>
</jmx>
</security>
|
Virtualhosts
This section allows you to define the set of virtual hosts which will be contained in your broker instance, and the message store & location for each. NB: The commented out section referencing BDBMessageStore should be used for all applications wishing to use persistence to disk.
...