[
https://issues.apache.org/jira/browse/CXF-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507288#comment-13507288
]
Sergey Beryozkin commented on CXF-4478:
---------------------------------------
Let me try it differently. I'm OK with getting 1.0 code extended to support
custom parameters. But I need to see the actual use (with some basic example)
of these custom parameters across all the 3-leg flow because it will affect the
way the code might get enhanced.
If you really need this extension then please simply type here a sample flow,
the way you envisage it working for your own application.
Example, "1. client requests RT and includes a custom parameter 2. it gets a RT
key back 3. redirects the user 4. gets the RT token verifier back 5. exchanges
RT for AT 6. uses AT to access a protected resource". I need to see at which
steps (2-6) the custom parameter submitted at step 1 is used.
> [OAuth1.0] RequestTokenHandler doesn't support custom input parameters
> ----------------------------------------------------------------------
>
> Key: CXF-4478
> URL: https://issues.apache.org/jira/browse/CXF-4478
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS Security
> Affects Versions: 2.6.1
> Reporter: Evgeni Kisel
>
> According to the spec custom parameters can be added but currnnelty it's
> impossible to use them because:
> 1. there are no hooks in the handle class to be overridden.
> 2. RequestTokenRegistration object doesn't contain a map with custom
> parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
