Github user k-wall commented on the issue:
https://github.com/apache/qpid-dispatch/pull/371
I manually tested the patch
https://github.com/apache/qpid-dispatch/pull/371 against Artemis 2.6.2,
Broker-J 7.0.6 and CPP Broker (master). The new behaviour looks good to me.
btw
GitHub user k-wall opened a pull request:
https://github.com/apache/qpid-proton/pull/152
PROTON-1886: Dump the thread's SSL error queue in the event that SSL_new
fails.
Uses the established mechanism to dump the thread's SSL error queue to
established tracer in the event
Github user k-wall commented on the issue:
https://github.com/apache/qpid-broker-j/pull/9
Olivier, thanks for the PR, but QPID-8208 appears to be a typo (it relates
to LDAP auth provider error handling rather than this problem). Can you correct
and we'll review
GitHub user k-wall opened a pull request:
https://github.com/apache/qpid-jms/pull/16
QPIDJMS-372: [SASL] [XOAUTH2] Make access token validation comply witâ¦
Makes the client's validation of OAUTH-2 access tokens RFC-6749 compliant.
You can merge this pull request into a Git
Github user k-wall commented on the issue:
https://github.com/apache/qpid-broker-j/pull/4
Hello Olivier
Thanks for the contribution. It is much appreciated.
I am not too uncomfortable with the idea of special casing of the state
behaviour for this one type
Github user k-wall commented on the issue:
https://github.com/apache/qpid-jms/pull/9
I have refreshed the pull request and added a test case around
AmqpSaslAuthenticator.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user k-wall commented on the issue:
https://github.com/apache/qpid-jms/pull/9
Tim, I have addressed your comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
GitHub user k-wall opened a pull request:
https://github.com/apache/qpid-jms/pull/9
QPIDJMS-294: Ensure that SASL mechanism has completed before allowingâ¦
⦠authentication to complete successfully
This change allows the SCRAM mechanisms to ensure that server final
GitHub user k-wall opened a pull request:
https://github.com/apache/qpid-proton-j/pull/9
PROTON-1486: Expose SaslOutcome additional-data to users of the API
Based on original work by rgodfrey <rgodf...@apache.org>
Having reviewed the existing API, it seemed r
