Problem after company internal deployment

[Daniel Koller]

Dear colleagues,

I installed ESME on a server inside the company network. After solving
an proxy issue (prohibiting openid requests leaving the company
network), I can logon with an openid, but after the request is
forwarded back to the esme app, I get the following exception:

Oct 28, 2008 6:13:45 PM org.apache.catalina.core.StandardWrapperValve
invoke
SEVERE: Servlet.service() for servlet default threw exception
org.openid4java.message.MessageException: Invalid set of parameters
for the requested message type
at
org.openid4java.message.AuthSuccess.createAuthSuccess(AuthSuccess.java:
116)
at
org.openid4java.consumer.ConsumerManager.verify(ConsumerManager.java:
1110)
at net.liftweb.openid.OpenIDConsumer
$class.verifyResponse(OpenId.scala:284)
at us.esme.model.ESMEOpenIDConsumer.verifyResponse(User.scala:176)
at net.liftweb.openid.OpenIdVendor$$anonfun$dispatchPf$1$$anonfun
$apply$8$$anonfun$apply$9.apply(OpenId.scala:142)
at net.liftweb.openid.OpenIdVendor$$anonfun$dispatchPf$1$$anonfun
$apply$8$$anonfun$apply$9.apply(OpenId.scala:140)
at net.liftweb.util.Full.flatMap(Can.scala:266)
at net.liftweb.openid.OpenIdVendor$$anonfun$dispatchPf$1$$anonfun
$apply$8.apply(OpenId.scala:140)
at net.liftweb.openid.OpenIdVendor$$anonfun$dispatchPf$1$$anonfun
$apply$8.apply(OpenId.scala:139)
at net.liftweb.http.LiftServlet.liftedTree1$1(LiftServlet.scala:191)
at net.liftweb.http.LiftServlet.net$liftweb$http$LiftServlet$
$dispatchStatefulRequest(LiftServlet.scala:189)
at net.liftweb.http.LiftServlet$$anonfun$1.apply(LiftServlet.scala:
161)
at net.liftweb.http.LiftServlet$$anonfun$1.apply(LiftServlet.scala:
161)
at net.liftweb.http.S$.net$liftweb$http$S$$wrapQuery(S.scala:379)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit$1$
$anonfun$apply$18.apply(S.scala:419)
at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:359)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$doAround
$1.apply(S.scala:360)
at net.liftweb.mapper.MetaProtoExtendedSession$myWrapper
$.apply(ProtoExtendedSession.scala:71)
at net.liftweb.http.S$.net$liftweb$http$S$$doAround(S.scala:360)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_nest2InnerInit
$1.apply(S.scala:417)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$.net$liftweb$http$S$$_nest2InnerInit(S.scala:
416)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$
$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply
$24$$anonfun$apply$25.apply(S.scala:436)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$
$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23$$anonfun$apply
$24.apply(S.scala:435)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$
$anonfun$apply$21$$anonfun$apply$22$$anonfun$apply$23.apply(S.scala:
434)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$
$anonfun$apply$21$$anonfun$apply$22.apply(S.scala:433)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit$1$
$anonfun$apply$21.apply(S.scala:432)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$net$liftweb$http$S$$_innerInit
$1.apply(S.scala:431)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$.net$liftweb$http$S$$_innerInit(S.scala:430)
at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$28$$anonfun
$apply$29$$anonfun$apply$30$$anonfun$apply$31.apply(S.scala:459)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$28$$anonfun
$apply$29$$anonfun$apply$30.apply(S.scala:458)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply$28$$anonfun
$apply$29.apply(S.scala:457)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$_init$1$$anonfun$apply
$28.apply(S.scala:456)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$$anonfun$_init$1.apply(S.scala:455)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.S$._init(S.scala:454)
at net.liftweb.http.S$.init(S.scala:322)
at net.liftweb.http.LiftServlet.doService(LiftServlet.scala:160)
at net.liftweb.http.LiftServlet$$anonfun$doIt
$1$1.apply(LiftServlet.scala:105)
at net.liftweb.http.LiftServlet$$anonfun$doIt
$1$1.apply(LiftServlet.scala:105)
at net.liftweb.util.TimeHelpers$class.calcTime(TimeHelpers.scala:227)
at net.liftweb.util.Helpers$.calcTime(Helpers.scala:26)
at net.liftweb.util.TimeHelpers$class.logTime(TimeHelpers.scala:236)
at net.liftweb.util.Helpers$.logTime(Helpers.scala:26)
at net.liftweb.http.LiftServlet.doIt$1(LiftServlet.scala:104)
at net.liftweb.http.LiftServlet.service(LiftServlet.scala:109)
at net.liftweb.http.LiftFilter$$anonfun$doFilter
$3.apply(LiftServlet.scala:476)
at net.liftweb.http.LiftFilter$$anonfun$doFilter
$3.apply(LiftServlet.scala:476)
at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:24)
at net.liftweb.http.URLRewriter$.doWith(RequestState.scala:341)
at net.liftweb.http.LiftFilter.doFilter(LiftServlet.scala:475)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:
235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:
206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:
191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:
102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
286)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:
845)
at org.apache.coyote.http11.Http11Protocol
$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:
447)
at java.lang.Thread.run(Unknown Source)

Has anybody of an idea, what the problem could be or where additional
debugging information can be retrieved?

Kind regards,

Daniel

[Hirsch, Richard]

I've tried with openId and with verisign openIDs and both lead to the same exception

-----Ursprüngliche Nachricht-----
Von: esme...@googlegroups.com [mailto:esme...@googlegroups.com] Im Auftrag von Daniel Koller
Gesendet: Mittwoch, 29. Oktober 2008 09:11
An: esme-dev
Betreff: [ESME-dev] Problem after company internal deployment

[Hirsch, Richard]

This is a known problem in openid4java (http://code.google.com/p/openid4java/issues/detail?id=65) that is already fixed in the trunk. The question is how we get the new openid4java code in ESME?

D.

-----Ursprüngliche Nachricht-----
Von: esme...@googlegroups.com [mailto:esme...@googlegroups.com] Im Auftrag von Daniel Koller
Gesendet: Mittwoch, 29. Oktober 2008 09:11
An: esme-dev
Betreff: [ESME-dev] Problem after company internal deployment

[Daniel Koller]

...does it make sense to to try to build the jars on my own? (then it
would be quite easy to replace the jars with the error)

Kind regards,

Daniel

On Oct 29, 9:36 am, "Hirsch, Richard" <richard.hir...@siemens.com>
wrote:

[Hirsch, Richard]

Currently, we are using openid4java-0.9.3.jar. We need
openid4java-0.9.4.jar. The problem is fixed there
(http://code.google.com/p/openid4java/source/browse/branches/openid4java
-0.9.4/src/org/openid4java/message/AuthSuccess.java?r=357)

Someone just needs to make the new openid4java-0.9.4.jar and then
distribute it. Then the problem should be solved.

Can someone (@dpp or @dhague) please do that.

D.

[Hirsch, Richard]

Here is the new 0.9.4 jar: http://code.sxip.com/openid4java/. You may have to rename it?

-----Ursprüngliche Nachricht-----
Von: esme...@googlegroups.com [mailto:esme...@googlegroups.com] Im Auftrag von Daniel Koller

Gesendet: Mittwoch, 29. Oktober 2008 09:48
An: esme-dev
Betreff: [ESME-dev] Re: Problem after company internal deployment

[Darren Hague]

There should be no need to rename the file - just remove the old file
from the War and put the new file in its place.

Cheers,
Darren

On Oct 29, 9:04 am, "Hirsch, Richard" <richard.hir...@siemens.com>

[David Pollak]

ESME uses Maven for its build process.  The name and version of the JAR files is listed in the pom.xml file.  ESME depends on Lift's openid provider.  Lift's openid provider relies on 0.9.3.  0.9.4 is not yet in the Maven repository.

Given that 0.9.4 is stable, it'd be great to get it into the appropriate repository.  I've cc'ed David Bernard who is Lift's Maven guru and also does Maven-related stuff for OpenID4Java.  I hope he'll have a chance to put 0.9.4 in the maven repository.  Once he does this, I'll update Lift to use 0.9.4 and we'll be good to go.

Thanks,

David

--
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

[David Pollak]

FYI

---------- Forwarded message ----------
From: David Bernard <david.be...@gmail.com>
Date: Wed, Oct 29, 2008 at 6:46 AM
Subject: Re: [ESME-dev] Re: Problem after company internal deployment
To: David Pollak <feeder.of...@gmail.com>
Cc: esme...@googlegroups.com


Hi,

The last time I check openid4java to provide jars with a correct pom,
the main issue was is that dependencies are spaghetti and depends of
some unreleased code (infocard).
I'll check again (before next monday) and if ok, I'll deploy
openid4java on scala-tools.org.

/davidB

[Daniel Koller]

Hi all,

just an info to conclude this topic: it worked after replacing the jar
file (without a need to rename the file),

Kind regards,

Daniel

Darren Hague wrote:
> There should be no need to rename the file - just remove the old file
> from the War and put the new file in its place.
>
> Cheers,
> Darren
>
> On Oct 29, 9:04�am, "Hirsch, Richard" <richard.hir...@siemens.com>
> wrote:
> > Here is the new 0.9.4 jar:http://code.sxip.com/openid4java/. You may have to rename it?
> >

> > -----Urspr�ngliche Nachricht-----

> > Von: esme...@googlegroups.com [mailto:esme...@googlegroups.com] Im Auftrag von Daniel Koller
> > Gesendet: Mittwoch, 29. Oktober 2008 09:48
> > An: esme-dev
> > Betreff: [ESME-dev] Re: Problem after company internal deployment
> >
> > ...does it make sense to to try to build the jars on my own? (then it
> > would be quite easy to replace the jars with the error)
> >
> > Kind regards,
> >
> > Daniel
> >
> > On Oct 29, 9:36�am, "Hirsch, Richard" <richard.hir...@siemens.com>
> > wrote:
> >
> > > This is a known problem in openid4java (http://code.google.com/p/openid4java/issues/detail?id=65) that is already fixed in the trunk. The question is how we get the new openid4java code in ESME?
> >
> > > D.
> >

> > > -----Urspr�ngliche Nachricht-----

[Darren Hague]

That's great to hear - thanks for the update, Daniel.

Cheers,
Darren