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 "Ashok Shah (JIRA)" <fx...@ws.apache.org> on 2005/05/20 18:57:55 UTC

[jira] Updated: (WSFX-49) Imporving the property file handling for SAML Assertion. Adding it to protected method instead of private.

     [ http://issues.apache.org/jira/browse/WSFX-49?page=all ]

Ashok Shah updated WSFX-49:
---------------------------

    Attachment: difference.log

Attached is the difference for the fix to the reported problem. The code to load the instance of SAMLIssuer.java has been moved to a protected method. 

> Imporving the property file handling for SAML Assertion. Adding it to protected method instead of private.
> ----------------------------------------------------------------------------------------------------------
>
>          Key: WSFX-49
>          URL: http://issues.apache.org/jira/browse/WSFX-49
>      Project: WSFX
>         Type: Improvement
>   Components: WSS4J
>  Environment: Gentoo, java 1.5.0_03, 
>     Reporter: Ashok Shah
>     Priority: Critical
>  Attachments: difference.log
>
> The code to load the SAML Assertion Issuer is located in performSTAction and performST_SIGAction which have private access in org.apache.ws.security.handler.WSS4JHandler.java. The user cannot override the private method to load the custom issuer without specifying the property file. If the code to load the instance of org.apache.ws.security.saml.SAMLIssuer.java is in protected method, one could extend the WSS4JHandler.java and load the custom SAMLIssuer without the need of property file.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira