Need a driver that support Kerberos to deprecate QPID

[Davanum Srinivas (DIMS)]

Quote from Adam young on https://review.openstack.org/#/c/193804

You can't deprecate a driver without providing a viable alternative.
Right now, QPID is the only driver that supports Kerberos.
TO support Kerberos, tyou need support for the GSSAPI library, which is usually done via support for SASL. Why is it so convoluted...historical...
We've talked with both teams (I work with Ken) and I think Proton is likely going to be the first to have support. The folks working on Rabbit have the double hurdle of getting SASL support into Erlang first, and then support for SASL into Rabbit. They've indicated a preference for getting it in to the AMQP 1.0 driver, and not bothering with the exisiting, but, check me on this, the Oso.Messaging code only support the pre 1.0 Rabbit.
So..until we have a viable alternative, please leave QPID alone. I've not been bothering people about it, as there seems to be work to get ahead, but until either Rabbit or Proton support Kerberos, I need QPID as is.

[Ken Giusti (kgiusti)]

I believe this bug is addressed by the current amqp1 driver on master.

Adam - can you try GSSAPI using the latest version of the amqp:// driver in olso.messaging and see if it meets your needs?

I don't think Liberty currently has all the bugfixes necessary to satisfy this bug - perhaps it makes sense to backport fixes from master?

[Ken Giusti (kgiusti)]

Adam,

I've found a bug in the driver that prevents GSSAPI from working correctly:

https://bugs.launchpad.net/oslo.messaging/+bug/1503258

Hold off testing until I can patch this,

thanks.

[Adam Young (ayoung)]

Tested with updated code. Works correctly.

We can deprecate QPID in favor of AMQP and Proton.