[jira] [Created] (CXF-4425) [OAuth] enable to send multiple requests with the same header

Evgeni Kisel created CXF-4425: - Summary: [OAuth] enable to send multiple requests with the same header Key: CXF-4425 URL: https://issues.apache.org/jira/browse/CXF-4425 Project: CXF Issue Type:

[jira] [Commented] (CXF-4425) [OAuth] enable to send multiple requests with the same header

[ https://issues.apache.org/jira/browse/CXF-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415115#comment-13415115 ] Evgeni Kisel commented on CXF-4425: --- OAuth 1.0 1. I send the request to Service Provider

[jira] [Commented] (CXF-4425) [OAuth] enable to send multiple requests with the same header

[ https://issues.apache.org/jira/browse/CXF-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415137#comment-13415137 ] Evgeni Kisel commented on CXF-4425: --- 1. It's a service provider security violation. 2. OA

[jira] [Commented] (CXF-4425) OAuth 1.0 timestamp and nonces are not validated and the validation can not be customized

[ https://issues.apache.org/jira/browse/CXF-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415898#comment-13415898 ] Evgeni Kisel commented on CXF-4425: --- I'm apologize for my impudence but could you send me

[jira] [Created] (CXF-4428) [OAuth1.0] allow to set response codes when throwing exception from OAuthDataProvider implementation.

Evgeni Kisel created CXF-4428: - Summary: [OAuth1.0] allow to set response codes when throwing exception from OAuthDataProvider implementation. Key: CXF-4428 URL: https://issues.apache.org/jira/browse/CXF-4428

[jira] [Created] (CXF-4432) [OAuth1.0] oob callback is not supported

Evgeni Kisel created CXF-4432: - Summary: [OAuth1.0] oob callback is not supported Key: CXF-4432 URL: https://issues.apache.org/jira/browse/CXF-4432 Project: CXF Issue Type: Bug Componen

[jira] [Commented] (CXF-4425) OAuth 1.0 timestamp and nonces are not validated and the validation can not be customized

[ https://issues.apache.org/jira/browse/CXF-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420663#comment-13420663 ] Evgeni Kisel commented on CXF-4425: --- I'm sorry. I've made a quick look, seem it's fixed. W

[jira] [Comment Edited] (CXF-4425) OAuth 1.0 timestamp and nonces are not validated and the validation can not be customized

[ https://issues.apache.org/jira/browse/CXF-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420663#comment-13420663 ] Evgeni Kisel edited comment on CXF-4425 at 7/23/12 2:03 PM: I've

[jira] [Created] (CXF-4478) [OAuth1.0] RequestTokenHandler doesn't support custom input parameters

Evgeni Kisel created CXF-4478: - Summary: [OAuth1.0] RequestTokenHandler doesn't support custom input parameters Key: CXF-4478 URL: https://issues.apache.org/jira/browse/CXF-4478 Project: CXF Iss

[jira] [Commented] (CXF-4478) [OAuth1.0] RequestTokenHandler doesn't support custom input parameters

[ https://issues.apache.org/jira/browse/CXF-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500968#comment-13500968 ] Evgeni Kisel commented on CXF-4478: --- Hi, For example customizing 3-legged scenario for mo

[jira] [Commented] (CXF-4478) [OAuth1.0] RequestTokenHandler doesn't support custom input parameters

[ https://issues.apache.org/jira/browse/CXF-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501102#comment-13501102 ] Evgeni Kisel commented on CXF-4478: --- The initial idea is to provide "hook" for developers

[jira] [Commented] (CXF-4478) [OAuth1.0] RequestTokenHandler doesn't support custom input parameters

[ https://issues.apache.org/jira/browse/CXF-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503804#comment-13503804 ] Evgeni Kisel commented on CXF-4478: --- OAuth 1.0 must be used because it's more secure and h