oasis-wss-saml-token-profile-1.0 for Rampart/C

[Supun Kamburugamuva <su...@gmail.com>]

Hi all,

We have the SAML 1.1 model implemented for Rampart/C. Now I'm
implementing the oasis-wss-saml-token-profile-1.0 for Rampart/C. This
will allow sending of SAML assertion through SOAP messages. At the
moment I'm implementing the general methods required to support the
SAML assertion inclusion to SOAP messages like reference building and
reference processing methods.

The next step will be to define the public functionality that should
be given to the user. Unlike tokens like Username tokens, SAML
assertions (SAML tokens) should be passed to the service level for
specific processing. That is where the public functionality is
required.

Regards,
Supun.

Re: oasis-wss-saml-token-profile-1.0 for Rampart/C

[Kaushalye Kapuruge <ka...@wso2.com>]

Supun Kamburugamuva wrote:
> Hi all,
>
> We have the SAML 1.1 model implemented for Rampart/C. Now I'm
> implementing the oasis-wss-saml-token-profile-1.0 for Rampart/C. This
> will allow sending of SAML assertion through SOAP messages. At the
> moment I'm implementing the general methods required to support the
> SAML assertion inclusion to SOAP messages like reference building and
> reference processing methods.
>
> The next step will be to define the public functionality that should
> be given to the user. Unlike tokens like Username tokens, SAML
> assertions (SAML tokens) should be passed to the service level for
> specific processing. That is where the public functionality is
> required.
>   
Good work Supun. Let me  know if you need any assistance.
We need to extend our sample base to demo this new feature once done. 
What's your plan for that? Right now we use a single service and a 
client with multiple policy configurations. We might have to introduce a 
new service and a client I guess.
Cheers,
Kaushalye
> Regards,
> Supun.
>
>   


-- 
http://blog.kaushalye.org/
http://wso2.org/