Hi. I will continue in this thread to Finally it seems that we're going to
keep using the axis2 1.1 version so we don't have to recompilate everything.
I proved the sample05 example from the repository adjusting it for the
version 1.1 and I've found two problems: It seems that there's a problem
Thanks for your quick response. I'm going to put the examples to work.
Regards.
Christina.
2007/8/14, Ruchith Fernando [EMAIL PROTECTED]:
Hi Christina,
Rampart supports adding SAML Tokens to the security header in the
policy based implementation. You can see an example here :
Hi all Axis2 users:
I have been managing some web services using UsernameTokens (without using
rampart) to convey identities. I've a client that connects to a Token issuer
service that provides it an EndpointReference and the Username token needed
to authenticate. Now I must remodelate the
Hi Christina,
Check the contents under Setting up a Security Token Service
available at [1] if you want to set up Rahas. Another sample is
available at [2].
If you want to supply your own name identifier in the SAML token
please implement the CallbackHanlder like this[3] and specify it in
the
Hi Christina,
Rampart supports adding SAML Tokens to the security header in the
policy based implementation. You can see an example here :
http://marc.info/?l=axis-userm=118665642802630w=2
By the way note that this requires the service to express it
requirements in policy and this sample uses
