> >
> > I tried this and it works fine, but I can't solve one problem.
> >
> > The problem is as follows:
> >
> > [problem]
> > router1 connects to router2 through JMS Bridge Extension Swiftlet
> > as user-a. user-a is defined in router2 in group-a and group-a
> only
> > has Publish Grant to topic.b, but user-a can subscribe to topic.b
> > and
> > can read the messages in topic.b.
>
> Just checked it here -- it's a bug. I hope you can live with it the
> next 2
> weeks; the bug will be fixed in 2.0.
Sorry, misinformation, not a bug! I tested it with auth disabled.
Authentication works fine. Problem is the brigde, especially that it
caches connections for re-use under the factory name. In your case that is
plainsocket@router2. Therefore, if you create a bridging with plainsocket
for user-a and then creates a new bridging for user-b with the same
factory, it re-uses the previous created connection and the user-b bridge
has the rights of user-a.
Disabling the subscribe grant for user-a should resolve your problem.
--
Andreas Mueller, [EMAIL PROTECTED], IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ, JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
