Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [higgins-dev] Question on using Higgins STS and RelyingPartyDemoApp

Hello Delgado,

I believe it's fixed. The issue was with keystore configuration. 

-- 
thanks,
Alexander Yuhimenko

On Tue, 19 Jan 2010 11:59:59 -0500
"Delgado, Mirko" <Mirko.Delgado@xxxxxxxxx> wrote:

> Hi Jeesmon,
> 
> Thanks for your response.
> 
> It is my understanding that the STS issues a card/token.  The STS I am using is a Higgins environment STS -> https://higgins.eclipse.org/TokenService/.  I am using the Azigo desktop client to download an import the card.  The Azigo endpoint URL is ->  https://rh155.azigo.net/cardsync-new/services/RPPSServiceAIRICM.
> 
> I am then going to the Higgins RelyingPartyDemoApp (https://higgins.eclipse.org/RelyingPartyDemoApp/).  When I click the i-card link on the site, it invokes the Azigo desktop client.  I select/submit the previously downloaded card.  My expectation here is that the RelyingPartyDemoApp will bring be to a transition page that tells me I am logged in or shows me the claims submitted, but instead I get an error.
> 
> Does anyone know what I am doing wrong?
> 
> thanks for your help,
> 
> Mirko Delgado
> 
> 
> 
> -----Original Message-----
> From: higgins-dev-bounces@xxxxxxxxxxx on behalf of Jeesmon Jacob
> Sent: Tue 1/19/2010 10:14 AM
> To: Higgins (Trust Framework) Project developer discussions
> Subject: Re: [higgins-dev] Question on using Higgins STS and RelyingPartyDemoApp
>  
> Looks like Azigo's backend service couldn't connect to your STS to
> import/retrieve card/token. Is your STS local? Can others outside your n/w
> connect to it?
> 
> -Jeesmon
> 
> On Tue, Jan 19, 2010 at 9:16 AM, Delgado, Mirko <Mirko.Delgado@xxxxxxxxx>wrote:
> 
> >
> > Hello All,
> >
> > I am new to the Higgins community and still learning about all the
> > available server/client parts available.
> >
> > I have been looking at the sample Higgins STS and Higgins
> > RelyingPartyDemoApp.
> >
> > I am using the setup STS from https://higgins.eclipse.org/TokenService/ to
> > issue a card.  I am using Azigo to import this card.  I am then going to the
> > RelyingPartyDemoApp (https://higgins.eclipse.org/RelyingPartyDemoApp/) to
> > submit this card to perform a login.  It is my assumption that using the
> > issued card from the STS should allow me to login to the
> > RelyingPartyDemoApp.  Is my assumption correct?  I have installed all the
> > certificates as indicated as party of the RelyingPartyDemoApp.  Can someone
> > tell me what I am doing wrong?
> >
> > thanks for your help,
> >
> > Mirko Delgado
> >
> > ______________________________________________________________________
> > Disclaimer: This email message and any attachments are for the sole use of
> > the intended recipient(s) and may contain information that is confidential,
> > legally privileged or otherwise exempt from disclosure under applicable law.
> > If you are not the intended recipient(s) or have received this message in
> > error, you are instructed to immediately notify the sender by return email
> > and required to delete this message from your computer system. This
> > communication does not form any contractual obligation on behalf of the
> > sender, the sender's employer or such employer's parent company, affiliates
> > or subsidiaries.
> >
> > _______________________________________________
> > higgins-dev mailing list
> > higgins-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/higgins-dev
> >
> >
> 
> 
> 
> ______________________________________________________________________
> Disclaimer:  This email message and any attachments are for the sole use of the intended recipient(s) and may contain information that is confidential, legally privileged or otherwise exempt from disclosure under applicable law. If you are not the intended recipient(s) or have received this message in error, you are instructed to immediately notify the sender by return email and required to delete this message from your computer system. This communication does not form any contractual obligation on behalf of the sender, the sender's employer or such employer's parent company, affiliates or subsidiaries.



Back to the top