You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Juliusz Brzostek (JIRA)" <ji...@apache.org> on 2008/07/24 11:15:31 UTC
[jira] Created: (WSS-139) securementActions - UserTokenAction
(dissapearing username)
securementActions - UserTokenAction (dissapearing username)
-----------------------------------------------------------
Key: WSS-139
URL: https://issues.apache.org/jira/browse/WSS-139
Project: WSS4J
Issue Type: Bug
Components: WSS4J Handlers
Affects Versions: 1.5.4
Environment: Java 1.5, Windows XP
Reporter: Juliusz Brzostek
Assignee: Ruchith Udayanga Fernando
Hi All,
1. There is a problem with dissapearing username :(
a) username is set on "" (empty string) in line 39 of UsernameTokenAction class,
b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
c) and else body is run (line 130 of Wss4jHandler), with:
callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
Is there any reason to set ID with empty string instead of to use passed to method username?
2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a problem we spent much
time, becouse no one imagine that is passible to change major things without upgrading version of library :(
HTH
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Resolved: (WSS-139) securementActions - UserTokenAction
(dissapearing username)
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-139.
-------------------------------------
Resolution: Invalid
> securementActions - UserTokenAction (dissapearing username)
> -----------------------------------------------------------
>
> Key: WSS-139
> URL: https://issues.apache.org/jira/browse/WSS-139
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Handlers
> Affects Versions: 1.5.4
> Environment: Java 1.5, Windows XP
> Reporter: Juliusz Brzostek
> Assignee: Ruchith Udayanga Fernando
>
> Hi All,
> 1. There is a problem with dissapearing username :(
> a) username is set on "" (empty string) in line 39 of UsernameTokenAction class,
> b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
> c) and else body is run (line 130 of Wss4jHandler), with:
> callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
> Is there any reason to set ID with empty string instead of to use passed to method username?
> 2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a problem we spent much
> time, becouse no one imagine that is passible to change major things without upgrading version of library :(
> HTH
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-139) securementActions - UserTokenAction
(dissapearing username)
Posted by "Juliusz Brzostek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616414#action_12616414 ]
Juliusz Brzostek commented on WSS-139:
--------------------------------------
In addition:
I'm using wss4j via spring Wss4jInterceptor. The interceptor has been configured like this:
<bean id="wss4jInterceptor" class="org.springframework.ws.soap.security.wss4j.Wss4jSecurityInterceptor">
<property name="securementActions" value="UsernameToken"/>
<property name="securementUsername" value="some user"/>
<property name="securementPassword" value="some password"/>
<property name="securementPasswordType" value="PasswordText"/>
</bean>
The idea is to inject username/password to outgoing messages (with no any validation). So I do not need any other securementHandlers ;)
> securementActions - UserTokenAction (dissapearing username)
> -----------------------------------------------------------
>
> Key: WSS-139
> URL: https://issues.apache.org/jira/browse/WSS-139
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Handlers
> Affects Versions: 1.5.4
> Environment: Java 1.5, Windows XP
> Reporter: Juliusz Brzostek
> Assignee: Ruchith Udayanga Fernando
>
> Hi All,
> 1. There is a problem with dissapearing username :(
> a) username is set on "" (empty string) in line 39 of UsernameTokenAction class,
> b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
> c) and else body is run (line 130 of Wss4jHandler), with:
> callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
> Is there any reason to set ID with empty string instead of to use passed to method username?
> 2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a problem we spent much
> time, becouse no one imagine that is passible to change major things without upgrading version of library :(
> HTH
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Issue Comment Edited: (WSS-139) securementActions -
UserTokenAction (dissapearing username)
Posted by "Juliusz Brzostek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616414#action_12616414 ]
jerry edited comment on WSS-139 at 7/24/08 2:25 AM:
---------------------------------------------------------------
Additionally:
I'm using wss4j via spring Wss4jInterceptor (spring 2.5.4).
The interceptor has been configured like this:
<bean id="wss4jInterceptor" class="org.springframework.ws.soap.security.wss4j.Wss4jSecurityInterceptor">
<property name="securementActions" value="UsernameToken"/>
<property name="securementUsername" value="some user"/>
<property name="securementPassword" value="some password"/>
<property name="securementPasswordType" value="PasswordText"/>
</bean>
The idea is to inject username/password to outgoing messages (with no any validation). So I do not need any other securementHandlers ;)
was (Author: jerry):
In addition:
I'm using wss4j via spring Wss4jInterceptor. The interceptor has been configured like this:
<bean id="wss4jInterceptor" class="org.springframework.ws.soap.security.wss4j.Wss4jSecurityInterceptor">
<property name="securementActions" value="UsernameToken"/>
<property name="securementUsername" value="some user"/>
<property name="securementPassword" value="some password"/>
<property name="securementPasswordType" value="PasswordText"/>
</bean>
The idea is to inject username/password to outgoing messages (with no any validation). So I do not need any other securementHandlers ;)
> securementActions - UserTokenAction (dissapearing username)
> -----------------------------------------------------------
>
> Key: WSS-139
> URL: https://issues.apache.org/jira/browse/WSS-139
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Handlers
> Affects Versions: 1.5.4
> Environment: Java 1.5, Windows XP
> Reporter: Juliusz Brzostek
> Assignee: Ruchith Udayanga Fernando
>
> Hi All,
> 1. There is a problem with dissapearing username :(
> a) username is set on "" (empty string) in line 39 of UsernameTokenAction class,
> b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
> c) and else body is run (line 130 of Wss4jHandler), with:
> callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
> Is there any reason to set ID with empty string instead of to use passed to method username?
> 2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a problem we spent much
> time, becouse no one imagine that is passible to change major things without upgrading version of library :(
> HTH
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Commented: (WSS-139) securementActions - UserTokenAction
(dissapearing username)
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616941#action_12616941 ]
Colm O hEigeartaigh commented on WSS-139:
-----------------------------------------
This is an issue with the spring framework, and not wss4j. In any case, this problem appears to have been fixed:
http://jira.springframework.org/browse/SWS-365
http://static.springframework.org/spring-ws/sites/1.5/xref/org/springframework/ws/soap/security/wss4j/Wss4jHandler.html
> securementActions - UserTokenAction (dissapearing username)
> -----------------------------------------------------------
>
> Key: WSS-139
> URL: https://issues.apache.org/jira/browse/WSS-139
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Handlers
> Affects Versions: 1.5.4
> Environment: Java 1.5, Windows XP
> Reporter: Juliusz Brzostek
> Assignee: Ruchith Udayanga Fernando
>
> Hi All,
> 1. There is a problem with dissapearing username :(
> a) username is set on "" (empty string) in line 39 of UsernameTokenAction class,
> b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
> c) and else body is run (line 130 of Wss4jHandler), with:
> callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
> Is there any reason to set ID with empty string instead of to use passed to method username?
> 2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a problem we spent much
> time, becouse no one imagine that is passible to change major things without upgrading version of library :(
> HTH
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
[jira] Closed: (WSS-139) securementActions - UserTokenAction
(dissapearing username)
Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed WSS-139.
-----------------------------------
> securementActions - UserTokenAction (dissapearing username)
> -----------------------------------------------------------
>
> Key: WSS-139
> URL: https://issues.apache.org/jira/browse/WSS-139
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Handlers
> Affects Versions: 1.5.4
> Environment: Java 1.5, Windows XP
> Reporter: Juliusz Brzostek
> Assignee: Ruchith Udayanga Fernando
>
> Hi All,
> 1. There is a problem with dissapearing username :(
> a) username is set on "" (empty string) in line 39 of UsernameTokenAction class,
> b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
> c) and else body is run (line 130 of Wss4jHandler), with:
> callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
> Is there any reason to set ID with empty string instead of to use passed to method username?
> 2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a problem we spent much
> time, becouse no one imagine that is passible to change major things without upgrading version of library :(
> HTH
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org