You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "Chris Rose (JIRA)" <ji...@apache.org> on 2008/07/09 23:37:31 UTC
[jira] Created: (RAMPARTC-117) SAML issued_token_acquire_function
should have an application context parameter
SAML issued_token_acquire_function should have an application context parameter
-------------------------------------------------------------------------------
Key: RAMPARTC-117
URL: https://issues.apache.org/jira/browse/RAMPARTC-117
Project: Rampart/C
Issue Type: Improvement
Components: Rampart-core
Affects Versions: 1.3.0
Environment: Rampart/C 1.2.0
Reporter: Chris Rose
Assignee: Malinda Kaushalye Kapuruge
In order to support binding the Rampart/C API into our scripting environment it is necessary to supply an interpreter context to the SAML issued_token_acquire callback, but no such capability exists. Without this it is not possible to bind the Rampart/C SAML API into languages outside of C. The function ostensibly accepts a context object, but in practice that is simply the rampart_context which cannot be extended to include complex objects such as scripting engine constructs.
In practice what would be ideal is something like this:
AXIS2_EXTERN axis2_status_t AXIS2_CALL
rampart_config_set_issued_token_aquire_function(rampart_config_t *rampart_config,
const axutil_env_t *env,
issued_token_callback_func issued_token_aquire,
void *context);
And then change the callback function to look like this:
typedef rampart_issued_token_t *(AXIS2_CALL * issued_token_callback_func)(
const axutil_env_t *env,
rp_property_t *issued_token,
rampart_context_t *rampart_context,
void *ctx);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (RAMPARTC-117) SAML issued_token_acquire_function
should have an application context parameter
Posted by "Milinda Lakmal Pathirage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milinda Lakmal Pathirage reassigned RAMPARTC-117:
-------------------------------------------------
Assignee: Milinda Lakmal Pathirage (was: Malinda Kaushalye Kapuruge)
> SAML issued_token_acquire_function should have an application context parameter
> -------------------------------------------------------------------------------
>
> Key: RAMPARTC-117
> URL: https://issues.apache.org/jira/browse/RAMPARTC-117
> Project: Rampart/C
> Issue Type: Improvement
> Components: Rampart-core
> Affects Versions: 1.3.0
> Environment: Rampart/C 1.2.0
> Reporter: Chris Rose
> Assignee: Milinda Lakmal Pathirage
> Priority: Minor
>
> In order to support binding the Rampart/C API into our scripting environment it is necessary to supply an interpreter context to the SAML issued_token_acquire callback, but no such capability exists. Without this it is not possible to bind the Rampart/C SAML API into languages outside of C. The function ostensibly accepts a context object, but in practice that is simply the rampart_context which cannot be extended to include complex objects such as scripting engine constructs.
> In practice what would be ideal is something like this:
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> rampart_config_set_issued_token_aquire_function(rampart_config_t *rampart_config,
> const axutil_env_t *env,
> issued_token_callback_func issued_token_aquire,
> void *context);
> And then change the callback function to look like this:
> typedef rampart_issued_token_t *(AXIS2_CALL * issued_token_callback_func)(
> const axutil_env_t *env,
> rp_property_t *issued_token,
> rampart_context_t *rampart_context,
> void *ctx);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPARTC-117) SAML issued_token_acquire_function
should have an application context parameter
Posted by "Chris Rose (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Rose updated RAMPARTC-117:
--------------------------------
Priority: Minor (was: Major)
> SAML issued_token_acquire_function should have an application context parameter
> -------------------------------------------------------------------------------
>
> Key: RAMPARTC-117
> URL: https://issues.apache.org/jira/browse/RAMPARTC-117
> Project: Rampart/C
> Issue Type: Improvement
> Components: Rampart-core
> Affects Versions: 1.3.0
> Environment: Rampart/C 1.2.0
> Reporter: Chris Rose
> Assignee: Malinda Kaushalye Kapuruge
> Priority: Minor
>
> In order to support binding the Rampart/C API into our scripting environment it is necessary to supply an interpreter context to the SAML issued_token_acquire callback, but no such capability exists. Without this it is not possible to bind the Rampart/C SAML API into languages outside of C. The function ostensibly accepts a context object, but in practice that is simply the rampart_context which cannot be extended to include complex objects such as scripting engine constructs.
> In practice what would be ideal is something like this:
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> rampart_config_set_issued_token_aquire_function(rampart_config_t *rampart_config,
> const axutil_env_t *env,
> issued_token_callback_func issued_token_aquire,
> void *context);
> And then change the callback function to look like this:
> typedef rampart_issued_token_t *(AXIS2_CALL * issued_token_callback_func)(
> const axutil_env_t *env,
> rp_property_t *issued_token,
> rampart_context_t *rampart_context,
> void *ctx);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPARTC-117) SAML issued_token_acquire_function
should have an application context parameter
Posted by "Milinda Lakmal Pathirage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613680#action_12613680 ]
Milinda Lakmal Pathirage commented on RAMPARTC-117:
---------------------------------------------------
This is something we have missed when implementing SAML support for Rampart/C. Thanks for pointing out this. I'll have look on to that ASAP.
> SAML issued_token_acquire_function should have an application context parameter
> -------------------------------------------------------------------------------
>
> Key: RAMPARTC-117
> URL: https://issues.apache.org/jira/browse/RAMPARTC-117
> Project: Rampart/C
> Issue Type: Improvement
> Components: Rampart-core
> Affects Versions: 1.3.0
> Environment: Rampart/C 1.2.0
> Reporter: Chris Rose
> Assignee: Malinda Kaushalye Kapuruge
> Priority: Minor
>
> In order to support binding the Rampart/C API into our scripting environment it is necessary to supply an interpreter context to the SAML issued_token_acquire callback, but no such capability exists. Without this it is not possible to bind the Rampart/C SAML API into languages outside of C. The function ostensibly accepts a context object, but in practice that is simply the rampart_context which cannot be extended to include complex objects such as scripting engine constructs.
> In practice what would be ideal is something like this:
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> rampart_config_set_issued_token_aquire_function(rampart_config_t *rampart_config,
> const axutil_env_t *env,
> issued_token_callback_func issued_token_aquire,
> void *context);
> And then change the callback function to look like this:
> typedef rampart_issued_token_t *(AXIS2_CALL * issued_token_callback_func)(
> const axutil_env_t *env,
> rp_property_t *issued_token,
> rampart_context_t *rampart_context,
> void *ctx);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.