You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/02/26 14:15:19 UTC
[jira] [Closed] (QPID-6965) Make preemptive HTTP authentication
pluggable
[ https://issues.apache.org/jira/browse/QPID-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy closed QPID-6965.
----------------------------
Closing all resolved 6.0.1 issues
> Make preemptive HTTP authentication pluggable
> ---------------------------------------------
>
> Key: QPID-6965
> URL: https://issues.apache.org/jira/browse/QPID-6965
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-6.0.1, qpid-java-6.1
>
> Attachments: fix-compilation-issue-on-6-0-branch.diff
>
>
> Currently the HTTP module includes the ability to support a preemptive {{Authorization: Basic-Auth <base64>}} authentication. (This is one where the client's request includes the Basic-Auth header providing correctly encoded credentials allowing the client's interaction with the Broker to be 'single-shot', without the need to separately authenticate a session). This is very useful when scripting with tools such as {{curl}}.
> This ability should be generalised so that other types of preemptive authentication can be supported too. One example would be a OAUTH's bearer authorization header {{Authorization: Bearer <token}}. See [https://tools.ietf.org/html/rfc6750#page-5].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org