You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Michael Bolz (JIRA)" <ji...@apache.org> on 2018/04/06 04:32:00 UTC
[jira] [Updated] (QPIDJMS-373) Support for OAuth flow and setting
of "Authorization" Header for WS upgrade request
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bolz updated QPIDJMS-373:
---------------------------------
Description:
Add support for OAuth flow ("client_credentials" and "password") (-and setting of "Authorization" Header- moved into [QPIDJMS-375|https://issues.apache.org/jira/browse/QPIDJMS-375]) during WebSocket connection handshake.
-Used "Authorization" Header or OAuth settings should/could be set via the "transport" parameters (TransportOptions).- (see above)
As PoC I created a [Fork|https://github.com/mibo/qpid-jms/tree/ws_add_header] and have done one commit for the [add of the Authorization Header|https://github.com/mibo/qpid-jms/commit/711052f0891556db0da6e7d68908b2f9dafadede] and one commit for the [OAuth flow|https://github.com/mibo/qpid-jms/commit/de70f0d3e4441358a239b3e776455201c133895d].
Hope this feature is not only interesting for me.
If yes, I will add the currently missing tests to my contribution and do a pull request.
Regards, Michael
was:
Add support for OAuth flow ("client_credentials" and "password") and setting of "Authorization" Header during WebSocket connection handshake.
Used "Authorization" Header or OAuth settings should/could be set via the "transport" parameters (TransportOptions).
As PoC I created a [Fork|https://github.com/mibo/qpid-jms/tree/ws_add_header] and have done one commit for the [add of the Authorization Header|https://github.com/mibo/qpid-jms/commit/711052f0891556db0da6e7d68908b2f9dafadede] and one commit for the [OAuth flow|https://github.com/mibo/qpid-jms/commit/de70f0d3e4441358a239b3e776455201c133895d].
Hope this feature is not only interesting for me.
If yes, I will add the currently missing tests to my contribution and do a pull request.
Regards, Michael
> Support for OAuth flow and setting of "Authorization" Header for WS upgrade request
> -----------------------------------------------------------------------------------
>
> Key: QPIDJMS-373
> URL: https://issues.apache.org/jira/browse/QPIDJMS-373
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Reporter: Michael Bolz
> Priority: Major
>
> Add support for OAuth flow ("client_credentials" and "password") (-and setting of "Authorization" Header- moved into [QPIDJMS-375|https://issues.apache.org/jira/browse/QPIDJMS-375]) during WebSocket connection handshake.
> -Used "Authorization" Header or OAuth settings should/could be set via the "transport" parameters (TransportOptions).- (see above)
>
> As PoC I created a [Fork|https://github.com/mibo/qpid-jms/tree/ws_add_header] and have done one commit for the [add of the Authorization Header|https://github.com/mibo/qpid-jms/commit/711052f0891556db0da6e7d68908b2f9dafadede] and one commit for the [OAuth flow|https://github.com/mibo/qpid-jms/commit/de70f0d3e4441358a239b3e776455201c133895d].
>
> Hope this feature is not only interesting for me.
> If yes, I will add the currently missing tests to my contribution and do a pull request.
>
> Regards, Michael
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org