[wsf-c-dev] [jira] Updated: (WSFPHP-294) Add Secure Conversation support

[Nandika Jayawardana (JIRA)]

     [ https://wso2.org/jira/browse/WSFPHP-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nandika Jayawardana updated WSFPHP-294:
---------------------------------------

    Description: 
SecureConversation sts will be implemented as a module in WSF/C. For a service to act as a sts, the user can set  the option "useOwnSTS"  to WSService class.

The usage of security context information will be handled using callback functions. The service will have the following predefined callback functions. 
bool storeSCTCallback(string localid, string global_id, string xml_string, [array userargs]);
bool deleteSCTCallback(string id, int type, [array useragrs]);
string getSCTCallback(string id, int type, bool is_encryption, [array userargs]);

The storeSCTCallback function stores the security context token string with the relevent id. deleteSCTCallback function deletes the security context token string with the given id.
getSCTCallback function returns the security context token string.


These callback functions will be added to the WSSecurityToken class.
The callbacks are same for the client and service. 
Secure conversation related configuration parameters should be specified using the relevent policy.


  was:
SecureConversation sts will be implemented as a module in WSF/C. For a service to act as a sts, the user can set  the option "useOwnSTS"  to WSService class.

The usage of security context information will be handled using callback functions. The service will have the following predefined callback functions. 
bool storeCallback(string localid, string global_id, string xml_string, [array userargs]);
bool deleteCallback(string id, int type, [array useragrs]);
bool getCallback(string id, int type, [array userargs]);
These callback functions will be added to the WSSecurityToken class.

These callback functions enables the user to handle the security context information. 

The callbacks are same for the client and service. 
Secure conversation related configuration parameters should be specified using the relevent policy.



> Add Secure Conversation support
> -------------------------------
>
>                 Key: WSFPHP-294
>                 URL: https://wso2.org/jira/browse/WSFPHP-294
>             Project: WSO2 WSF/PHP
>          Issue Type: New Feature
>    Affects Versions: Current (nightly)
>         Environment: Any
>            Reporter: Nandika Jayawardana
>            Assignee: Nandika Jayawardana
>             Fix For: 2.0.0
>
>
> SecureConversation sts will be implemented as a module in WSF/C. For a service to act as a sts, the user can set  the option "useOwnSTS"  to WSService class.
> The usage of security context information will be handled using callback functions. The service will have the following predefined callback functions. 
> bool storeSCTCallback(string localid, string global_id, string xml_string, [array userargs]);
> bool deleteSCTCallback(string id, int type, [array useragrs]);
> string getSCTCallback(string id, int type, bool is_encryption, [array userargs]);
> The storeSCTCallback function stores the security context token string with the relevent id. deleteSCTCallback function deletes the security context token string with the given id.
> getSCTCallback function returns the security context token string.
> These callback functions will be added to the WSSecurityToken class.
> The callbacks are same for the client and service. 
> Secure conversation related configuration parameters should be specified using the relevent policy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira