You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Eoghan Glynn (JIRA)" <ji...@apache.org> on 2007/02/22 17:30:05 UTC
[jira] Created: (CXF-430) HTTPConduit support for non-preemptive
Basic Auth
HTTPConduit support for non-preemptive Basic Auth
-------------------------------------------------
Key: CXF-430
URL: https://issues.apache.org/jira/browse/CXF-430
Project: CXF
Issue Type: New Feature
Components: Transports
Reporter: Eoghan Glynn
Assigned To: Eoghan Glynn
The current client-side support for HTTP Basic authorization is just a place-holder, with the following short-comings:
- credentials are only passed pre-emptively, i.e. in advance of an actual 401 challenge
- the AuthorizationPolicy only allows a single username and password to be configured, without any reference to a particular realm or targetURI
- there is no specific handling of 401 challenges, or attempt to trasparently resend
- this are no hooks to allow the client application participate in the trust evaluation before handing out the username/password
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-430) HTTPConduit support for non-preemptive
Basic Auth
Posted by "Polar Humenn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523332 ]
Polar Humenn commented on CXF-430:
----------------------------------
Hey Dan,
Wow, I thought we took care of that a long time ago. I guess this was just
a bookkeeping thing. How's the release going?
Cheers,
-Polar
-------------------------------------------------------------------
Polar Humenn Adiron, LLC
mailto:polar@adiron.com 2-212 CST
Phone: 315-278-1648 Syracuse, NY 13244-4100
Fax: 315-443-4745 http://www.adiron.com
> HTTPConduit support for non-preemptive Basic Auth
> -------------------------------------------------
>
> Key: CXF-430
> URL: https://issues.apache.org/jira/browse/CXF-430
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Eoghan Glynn
> Assignee: Eoghan Glynn
> Fix For: 2.0.1
>
>
> The current client-side support for HTTP Basic authorization is just a place-holder, with the following short-comings:
> - credentials are only passed pre-emptively, i.e. in advance of an actual 401 challenge
> - the AuthorizationPolicy only allows a single username and password to be configured, without any reference to a particular realm or targetURI
> - there is no specific handling of 401 challenges, or attempt to trasparently resend
> - this are no hooks to allow the client application participate in the trust evaluation before handing out the username/password
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-430) HTTPConduit support for non-preemptive
Basic Auth
Posted by "Polar Humenn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501688 ]
Polar Humenn commented on CXF-430:
----------------------------------
All subtasks should be closed.
> HTTPConduit support for non-preemptive Basic Auth
> -------------------------------------------------
>
> Key: CXF-430
> URL: https://issues.apache.org/jira/browse/CXF-430
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Eoghan Glynn
> Assignee: Eoghan Glynn
>
> The current client-side support for HTTP Basic authorization is just a place-holder, with the following short-comings:
> - credentials are only passed pre-emptively, i.e. in advance of an actual 401 challenge
> - the AuthorizationPolicy only allows a single username and password to be configured, without any reference to a particular realm or targetURI
> - there is no specific handling of 401 challenges, or attempt to trasparently resend
> - this are no hooks to allow the client application participate in the trust evaluation before handing out the username/password
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-430) HTTPConduit support for non-preemptive
Basic Auth
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-430.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
> HTTPConduit support for non-preemptive Basic Auth
> -------------------------------------------------
>
> Key: CXF-430
> URL: https://issues.apache.org/jira/browse/CXF-430
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Eoghan Glynn
> Assignee: Eoghan Glynn
> Fix For: 2.0.1
>
>
> The current client-side support for HTTP Basic authorization is just a place-holder, with the following short-comings:
> - credentials are only passed pre-emptively, i.e. in advance of an actual 401 challenge
> - the AuthorizationPolicy only allows a single username and password to be configured, without any reference to a particular realm or targetURI
> - there is no specific handling of 401 challenges, or attempt to trasparently resend
> - this are no hooks to allow the client application participate in the trust evaluation before handing out the username/password
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.