Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 4318 invoked from network); 11 Mar 2008 11:26:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Mar 2008 11:26:15 -0000 Received: (qmail 54945 invoked by uid 500); 11 Mar 2008 11:26:05 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 54915 invoked by uid 500); 11 Mar 2008 11:26:04 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 54904 invoked by uid 99); 11 Mar 2008 11:26:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 04:26:04 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nuria.rg1@gmail.com designates 64.233.184.239 as permitted sender) Received: from [64.233.184.239] (HELO wr-out-0506.google.com) (64.233.184.239) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 11:25:28 +0000 Received: by wr-out-0506.google.com with SMTP id 69so1196316wra.16 for ; Tue, 11 Mar 2008 04:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=2B5ZnkapHPBdENo4G0EDzGjJs0AHXH0uFGCevGE8VAo=; b=rqjO7zc1bY+tZ1N8xpo2q3081hfUSX8SKk/u2Pm2v7fFwpBX/w1BGDbIngVrSY8kSyITNy4PEacZ12kU+cINyfn1+xIGBmG/z4E4zGAM6ga85tM/Hm9XLo8LyhyynFwtoBlZKYhq5gSuB2akwg+Ic7l0SeFRG7QXmJaaL3MtTOU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=wNGLWYzMKy8PfkGzGKGjMiMifNKUMem/rTxr+BgII0s58GyRbBKQV+0+QqIJRGhJn9fzfT42abMDBf6cDbaNgcXs9xaKJ6y9gdYAYD97uUAyYW0/uNx80QgKRE30Z8rfi3JQc0bZkR4O5m3+MI7gEUl7CGGXwJuzp8r+pUSLvYA= Received: by 10.142.232.20 with SMTP id e20mr2414952wfh.160.1205234737350; Tue, 11 Mar 2008 04:25:37 -0700 (PDT) Received: by 10.143.9.2 with HTTP; Tue, 11 Mar 2008 04:25:36 -0700 (PDT) Message-ID: Date: Tue, 11 Mar 2008 12:25:36 +0100 From: "=?ISO-8859-1?Q?Nuria_Rodr=EDguez_Garc=EDa?=" To: axis-user@ws.apache.org Subject: SAML token MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2036_19471436.1205234737315" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2036_19471436.1205234737315 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Ruchith, I'm working with SAML token and I can see that there is a STSClient class in "*org.apache.axis2.security.trust.client*.STSClient" but I'm using "* org.apache.rahas.client*.STSClient". What is the main difference between these classes? I don't understand why STS Service needs the provider service policy. Is it necessary? The requestSecurityToken method returns a token with assertion. Does it make sense to have more than one assertion in the response security token? Thanks, Nuria ------=_Part_2036_19471436.1205234737315 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

Hi Ruchith,

 

I'm working with SAML token and I can see that there is a STSClient class in "org.apache.axis2.security.trust.client.STSClient" but I'm using "org.apache.rahas.client.STSClient".

What is the main difference between these classes?

 

I don't understand why STS Service needs the provider service policy. Is it necessary?

The requestSecurityToken method returns a token with assertion. Does it make sense to have more than one assertion in the response security token?

 

 

Thanks,

Nuria

------=_Part_2036_19471436.1205234737315--