You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by ji...@apache.org on 2004/05/24 15:46:00 UTC

[jira] Created: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Mon, 24 May 2004 6:45 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Christof Soehngen (mailto:christof.soehngen@syracom.de)
       Date: Mon, 24 May 2004 6:46 AM
    Changes:
             Attachment changed to WSSecurityEngine.java.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/WSFX-8?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Mon, 24 May 2004 6:46 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Closed: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Posted by ji...@apache.org.
Message:

   The following issue has been closed.

   Resolver: Werner Dittmann
       Date: Wed, 2 Jun 2004 11:22 AM

See e-mail to ws-fx list regarding this issue.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Wed, 2 Jun 2004 11:22 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Christof Soehngen (mailto:christof.soehngen@syracom.de)
       Date: Mon, 24 May 2004 6:46 AM
    Changes:
             Attachment changed to WSDoAllReceiver.java.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/WSFX-8?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Mon, 24 May 2004 6:46 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Christof Soehngen (mailto:christof.soehngen@syracom.de)
       Date: Mon, 24 May 2004 6:46 AM
    Changes:
             Attachment changed to WSSAddUsernameToken.java.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/WSFX-8?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Mon, 24 May 2004 6:46 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Christof Soehngen (mailto:christof.soehngen@syracom.de)
       Date: Mon, 24 May 2004 6:45 AM
    Changes:
             Attachment changed to UsernameToken.java.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/WSFX-8?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Mon, 24 May 2004 6:45 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Updated: (WSFX-8) Suggestion for a more flexible handling of UsernameTokens

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Christof Soehngen (mailto:christof.soehngen@syracom.de)
       Date: Mon, 24 May 2004 6:46 AM
    Changes:
             Attachment changed to WSSecurityEngineResult.java.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/WSFX-8?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/WSFX-8

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: WSFX-8
    Summary: Suggestion for a more flexible handling of UsernameTokens
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: WSFX
 Components: 
             WSS4J

   Assignee: 
   Reporter: Christof Soehngen

    Created: Mon, 24 May 2004 6:45 AM
    Updated: Mon, 24 May 2004 6:46 AM
Environment: CVS snapshot from 2004-05-24

Description:
I suggest improving UsernameToken handling to allow the following: 
 - hook in WSDoAllReceiver for custom validation algorithms
 - conserve custom child-elements of the UsernameToken and pass them to the validation algorithm

Problems with the existing code are:
 - validation takes place WSSecurityEngine
 - additional custom elements of the UsernameToken are discarded

I therefore modified the following classes:
 - org.apache.ws.security.WSSecurityEngine.java:
	* Remove method handleUsernameToken()
	* Modify method processSecurityHeader (extraction of UsernameToken)
 - org.apache.ws.security.WSSecurityEngineResult.java:
	* Add attribute ut
	* Add constructor with username token
	* Add method getUsernameToken
 - org.apache.ws.security.message.WSAddUsernameToken.java:
	* Add method addCustomElement()
 - org.apache.ws.security.message.token.UsernameToken.java:
	* Modify constructor: Read custom elements from XML
	* Add attribute customElements
	* Add method getCustomElements()
	* Add method setCustomElements()
 - org.apache.ws.axis.security.WSDoAllReceiver.java:
	* Modify method invoke: call hook for validation of UsernameToken (verifyUsernameToken())
	* Add method verifyUsernameToken()

Any suggestions are welcome,
Christof


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira