Ok, I've gotten further but not quite far enough. I was populating users in an
LDIF and I didn't have the format correct for specifying encrypted & base64
encoded passwords. Changed it to:
| userPassword: blahblahblah
|
Where "blahblahblah" is an encrypted & base64 encoded password. All
documentation I saw always specified it as:
| userPassword: {MD5}blahblahblah
|
Anyway, now it looks like my users are being authenticated correctly against
the LDAP server but now I get this error:
| 2005-04-29 09:07:27,508 WARN
[org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
| javax.jms.JMSSecurityException: Connection not authorized to do durable
subscription on topic: myTopic
| at
org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:135)
| at
org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:816)
| at
org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:297)
| at org.jboss.mq.il.jvm.JVMServerIL.subscribe(JVMServerIL.java:314)
| at org.jboss.mq.Connection.addConsumer(Connection.java:863)
| at
org.jboss.mq.SpyConnectionConsumer.<init>(SpyConnectionConsumer.java:95)
| at
org.jboss.mq.SpyConnection.createDurableConnectionConsumer(SpyConnection.java:154)
| at
org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:672)
| at
org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:764)
| at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
| at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
|
Since my JMS user is in my LDAP server where do I specify JMS subscription
information? Currently there are only 2 StateManagers (JDBCStateManager and a
DynamicStateManager). Both state managers handle logins, passwords, client
ids, subscriptions. I don't want to specify user logins/passwords/client ids
in 2 places, just in LDAP. Currently I still have my StateManager MBean (which
the SecurityManager, DestinationManager, etc depends on) pointed to a
JDBCStateManager which has queries that hit up against a JMS_USERS (empty since
info is in LDAP), JMS_ROLES (empty since info is in LDAP), and
JMS_SUBSCRIPTIONS tables.
Anyone run across this and have any ideas? There's got to be a way to do
this...
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875911#3875911
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875911
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
