You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (Jira)" <ji...@apache.org> on 2020/03/18 07:18:00 UTC

[jira] [Closed] (WSS-659) SecurityContextToken validator set by wrong QName

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

Colm O hEigeartaigh closed WSS-659.
-----------------------------------

> SecurityContextToken validator set by wrong QName
> -------------------------------------------------
>
>                 Key: WSS-659
>                 URL: https://issues.apache.org/jira/browse/WSS-659
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Axis Integration
>    Affects Versions: 2.2.4
>            Reporter: Igor Konoplyanko
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>             Fix For: 2.1.13, 2.3.0, 2.2.5
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> SecurityContextToken validator is set in apache cxf using properties:
>  properties.put(SCT_TOKEN_VALIDATOR, "someValidator");
>   
>  But it can't be used because SecurityContextTokeinInputHandler looks it up via other QName. wss4j sets it as {noformat}{http://schemas.xmlsoap.org/ws/2005/02/sc}Identifier{noformat} and CXF sets it as {noformat}{http://schemas.xmlsoap.org/ws/2005/02/sc}SecurityContextToken{noformat}.
>  
> {noformat}
> org.apache.cxf.ws.security.wss4j.WSS4JStaxInInterceptor#setTokenValidators
> if (validator != null) { 
>    properties.addValidator(WSSConstants.TAG_WSC0502_SCT, validator); 
>    properties.addValidator(WSSConstants.TAG_WSC0512_SCT, validator); 
> }
> {noformat}
> {noformat}
> WSS4J Part: SecurityContextTokenInputHandler.java:72 
> SecurityContextTokenValidator securityContextTokenValidator = wssSecurityProperties.getValidator(elementName); 
> if (securityContextTokenValidator == null) {
>   securityContextTokenValidator = new SecurityContextTokenValidatorImpl();        
> }
> {noformat}
>  
> I am still not sure where this problem should be fixed - on CXF or on wss4j side?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org