You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Dan Price (JIRA)" <ji...@apache.org> on 2012/07/18 22:03:34 UTC

[jira] [Created] (WSS-398) Can't create a UsernameToken without a password

Dan Price created WSS-398:
-----------------------------

             Summary: Can't create a UsernameToken without a password
                 Key: WSS-398
                 URL: https://issues.apache.org/jira/browse/WSS-398
             Project: WSS4J
          Issue Type: Bug
          Components: WSS4J Handlers
    Affects Versions: 1.6.6
            Reporter: Dan Price
            Assignee: Colm O hEigeartaigh


WSHandler: application provided null or empty password message when trying to send a UsernameToken with passwordType == PasswordNone.  Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.  This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Commented] (WSS-398) Can't create a UsernameToken without a password

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WSS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418347#comment-13418347 ] 

Colm O hEigeartaigh commented on WSS-398:
-----------------------------------------


This is now fixed.

Colm.
                
> Can't create a UsernameToken without a password
> -----------------------------------------------
>
>                 Key: WSS-398
>                 URL: https://issues.apache.org/jira/browse/WSS-398
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.6.6
>            Reporter: Dan Price
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.6.7
>
>
> "WSHandler: application provided null or empty password" message when trying to send a UsernameToken with passwordType == PasswordNone.
> Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.
> This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Updated] (WSS-398) Can't create a UsernameToken without a password

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated WSS-398:
------------------------------------

    Fix Version/s: 1.6.7
    
> Can't create a UsernameToken without a password
> -----------------------------------------------
>
>                 Key: WSS-398
>                 URL: https://issues.apache.org/jira/browse/WSS-398
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.6.6
>            Reporter: Dan Price
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.6.7
>
>
> "WSHandler: application provided null or empty password" message when trying to send a UsernameToken with passwordType == PasswordNone.
> Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.
> This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Resolved] (WSS-398) Can't create a UsernameToken without a password

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh resolved WSS-398.
-------------------------------------

    Resolution: Fixed
    
> Can't create a UsernameToken without a password
> -----------------------------------------------
>
>                 Key: WSS-398
>                 URL: https://issues.apache.org/jira/browse/WSS-398
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.6.6
>            Reporter: Dan Price
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.6.7
>
>
> "WSHandler: application provided null or empty password" message when trying to send a UsernameToken with passwordType == PasswordNone.
> Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.
> This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Closed] (WSS-398) Can't create a UsernameToken without a password

Posted by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed WSS-398.
-----------------------------------

    
> Can't create a UsernameToken without a password
> -----------------------------------------------
>
>                 Key: WSS-398
>                 URL: https://issues.apache.org/jira/browse/WSS-398
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.6.6
>            Reporter: Dan Price
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.6.7
>
>
> "WSHandler: application provided null or empty password" message when trying to send a UsernameToken with passwordType == PasswordNone.
> Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.
> This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] [Updated] (WSS-398) Can't create a UsernameToken without a password

Posted by "Dan Price (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WSS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Price updated WSS-398:
--------------------------

    Description: 
"WSHandler: application provided null or empty password" message when trying to send a UsernameToken with passwordType == PasswordNone.

Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.

This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

  was:WSHandler: application provided null or empty password message when trying to send a UsernameToken with passwordType == PasswordNone.  Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.  This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

    
> Can't create a UsernameToken without a password
> -----------------------------------------------
>
>                 Key: WSS-398
>                 URL: https://issues.apache.org/jira/browse/WSS-398
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Handlers
>    Affects Versions: 1.6.6
>            Reporter: Dan Price
>            Assignee: Colm O hEigeartaigh
>
> "WSHandler: application provided null or empty password" message when trying to send a UsernameToken with passwordType == PasswordNone.
> Seems to be happening because WSHandler doesn't rcognize this as possible, even though password is optional.
> This is a regression of sorts, as this same problem was fixed in previous versions.  The UsernameToken.setPassword method has a check to allow this, but the getPasswordCB method is checking before this and claiming it's an error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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