Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 25 Jul 2014 19:50:40 +0000 (UTC)
From: "Jan Bernhardt (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12729838.1406317052861.47094.1406317840487@arcas>
In-Reply-To: <JIRA.12729838.1406317052861@arcas>
References: <JIRA.12729838.1406317052861@arcas>
Subject: [jira] [Closed] (CXF-5907) Full claim mapping enforcement in
 federated scenario
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bernhardt closed CXF-5907.
------------------------------

    Resolution: Not a Problem

Ups, sorry for the noise. This is not a bug. All works as it should be ;)

> Full claim mapping enforcement in federated scenario
> ----------------------------------------------------
>
>                 Key: CXF-5907
>                 URL: https://issues.apache.org/jira/browse/CXF-5907
>             Project: CXF
>          Issue Type: Bug
>          Components: STS
>    Affects Versions: 2.7.12, 3.0.1
>            Reporter: Jan Bernhardt
>              Labels: claims, sts
>
> In case of federation claims can be mapped from one realm to another. Mapping can also include that some claim values are not relevant/desired for the target realm and thus should be omitted in the new token. However the {{org.apache.cxf.sts.claims.ClaimsManager}} enforces currently that all claim types contained in the request also must be included in the response by calling {{validateClaimValues(claims, targetClaims);}} at the end of the claim mapping. If some claim types have not been mapped to the new token, an exception is thrown. Therefore this check should be removed to allow mappings with different claim types in request and response.


--
This message was sent by Atlassian JIRA
(v6.2#6252)