> As adding "swiftmqmgmt@router-b" entity is operated in company-a, it
> can be
> a security problem from company-b standpoint.
>
> 1. We tried to avoid this problem by configuring host access list of
> router-b.
> -> We can reduce the security risks, but we still need to add
> router.company-a.com
> to host access list. It seems it means router-b allows router-a
> not only to
> connect to but also to controll router-b.
> 2. We looked for access controll capability of management swiftlet.
> -> We counldn't find that.
>
> Is there any way to allow a router only to connect to the router ?
No. The authentication is completly local performed. Thus, if you have
access to router-a from b, b decides about the authentication. In a future
version we will add distributed authentication.
--
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/
