shibboleth-dev - missing loginContext.getRelyingPartyId()
Subject: Shibboleth Developers
List archive
- From: Jukka Hakosalo <>
- To:
- Subject: missing loginContext.getRelyingPartyId()
- Date: Wed, 18 Feb 2009 21:05:09 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=vZ8Q3ZxbTdPQ+KF89hgbntYKl05d5MNE6dkaRAYsFb900CsuN6MG05ARarhm94eNG+ JB8e6tdUQAjfzx5KCcRWhvUPD1xsekaVy0UlfBFhls3NwZEliYulAUufcoOJ83zVO3aM Ehi0Kcoe2aJwExzXSUxUUQI2D+JT0wiy898Uw=
Hello,
We are starting to use idp version 2.1. It uses Tomcat's form
authentication. Where can I find the information, which sp is trying
to contact our idp?
Our idp1.3 gets that information from a SSO request:
https://idp.com/shibboleth/SSO?providerId=THIS_HERE&target...
Our new idp also uses tomcat's form login. I've been trying to catch
that missing providerId-paramater like this:
LoginContext loginContext =
(LoginContext)request.getAttribute(LoginContext.LOGIN_CONTEXT_KEY);
String entityId = loginContext.getRelyingPartyId();
This code was in login.jsp and then in tomcats
formauthentication-class. LoginContext is null.
Regards,
Jukka
- missing loginContext.getRelyingPartyId(), Jukka Hakosalo, 02/18/2009
- Re: [Shib-Dev] missing loginContext.getRelyingPartyId(), Chad La Joie, 02/19/2009
Archive powered by MHonArc 2.6.16.