[TYRUS-228] Add client support for HTTP Basic/Digest Created: 02/Aug/13  Updated: 08/Jul/14

Status: Open
Project: tyrus
Component/s: None
Affects Version/s: None
Fix Version/s: 1.x-backlog

Type: New Feature Priority: Major
Reporter: Pavel Bucek Assignee: Ondrej Kosatka
Resolution: Unresolved Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by TYRUS-303 Add support for HTTP BASIC and DIGEST... Resolved

 Description   

Some support for generating required headers (user would just set username, password, realm, .. and method (BASIC|DIGEST)). Preemptive authorization might be a good start.



 Comments   
Comment by Siva [ 07/Jun/14 ]

Authentication and Authorization are very much important for enterprise applications and we can not give any exceptions for those features for any network interfacing applications.
looking forward to see easy to configure built in API to enable Authentication with SSO, Basic etc...
This will improve Tyrus usage in security critical applications.

Comment by Shinta. [ 08/Jul/14 ]

Our proxy requires Digest authentication scheme.
I hope that this issue is resolved.

Comment by Pavel Bucek [ 08/Jul/14 ]

Hi Shinta.

This issue is not resolved yet and even when it will be, it won't help with the proxy authentication. We have different issue filed about that (please see https://java.net/jira/browse/TYRUS-204). Tyrus client currently provides access to headers which will be sent in a request which is used for connection to the proxy and any auth header can be added this way.

We plan to extend functionality from this issue (when it is done) to the one with proxies, but it won't be done as part of this task.

Regards,
Pavel

Comment by Shinta. [ 08/Jul/14 ]

Thank you for your reply.
I'll make sure of other issue(https://java.net/jira/browse/TYRUS-204).

Generated at Fri Jul 11 21:13:30 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.