cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Bernhardt (Created) (JIRA)" <>
Subject [jira] [Created] (CXF-4062) Enabling custom claim parser
Date Wed, 25 Jan 2012 09:20:42 GMT
Enabling custom claim parser

                 Key: CXF-4062
             Project: CXF
          Issue Type: Improvement
    Affects Versions: 2.5.2
            Reporter: Jan Bernhardt

Currently there is now way to use a custom dialect in requested claims. Even
is not fully supported (only ClaimType element).

Therefore I introduced a new Interface ClaimParser, and a DefaultClaimParser with the current
parsing logic. This parser is called by default within RequestParser, so that the normal cxf
behavior has not changed. But to make this process more flexible it is possible (with this
patch) to register any kind of ClaimParser supporting a specific dialect. I implemented a
IdentityClaimParser which is currently able to parser CustomType and CustomValueType elements
within the wst:claims element. Since the current RequestClaim does not support any claim values,
except of the Uri attribute, I created a SubClass ClaimValueType to also pass the claim value
to the claim handler.

This patch is just a starting point. I think there should be a more complex redesign of the
current claim handling implementation, because it is currently focused on only one Use-Case.
The following improvements should be made:
* The RequestClaim class should be replaced by a more flexible interface supporting any kind
of parsing and handling custom dialects.
* It should be possible to include/configure custom claimparser via spring config
* A fully supported implementation of
dialect would be great

Here is an example of a claims STS request which is supported by applying this patch:
<wst:Claims Dialect="" xmlns:ic="">
  <ic:ClaimValue Uri=""/>admin</ic:ClaimValue>

Thank you for this great product!! I hope this patch can help to further improve CXF.

Best regards

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message