On Tue, 2018-10-16 at 09:40 -0400, Ganesh Murthy wrote: > The Apache Qpid (http://qpid.apache.org) community is pleased to > announce the immediate availability of Apache Qpid Dispatch 1.4.0 > > Qpid Dispatch is a router for the Advanced Message Queuing Protocol 1.0 > (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It provides a flexible > and scalable interconnect between AMQP endpoints, whether they be clients, > brokers, or other AMQP-enabled services. > > The release is available now from our website: > https://qpid.apache.org/releases/qpid-dispatch-1.4.0/index.html > > Release notes can be found at: > http://qpid.apache.org/releases/qpid-dispatch-1.4.0/release-notes.html >
https://issues.apache.org/jira/browse/DISPATCH-1111 has changed the place of where Dispatch Router (1.4.0) expects to find the authenticated identity within the connection properties. However, there is no way for an auth server to determine the Dispatch Router version that is trying to authenticate the user, so it is hard to implement an auth server that supports both Dispatch Router versions < 1.4 and >= 1.4. Is it policy to not include e.g. a version property in the connection properties when Dispatch Router opens/accepts a connection? Or maybe another desired capability value could be used for indicating that the Dispatch Router expects the identity to be contained in the "sub" entry instead of the "authenticated- identity" itself? > Thanks to all involved. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org >
