AlexKovic / openid4java

Automatically exported from code.google.com/p/openid4java
Apache License 2.0
0 stars 0 forks source link

problems with consumer-servlet: Yadis URL #45

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi, i successfully installed the consumer-servlet
example(java-openid-sxip-0.9.4.339 version) on my server (tomcat 6.0).
However, when i try to execute the application, i encounter the following
error: "A Yadis Resource Descriptor URL MUST be an absolute URL and it must
be HTTP or HTTPS; found: null"

here is the application log:

5 déc. 2007 23:05:52 org.openid4java.consumer.ConsumerManager authenticate
INFO: Creating authentication request for OP-endpoint:
http://www.myopenid.com/server claimedID: http://matmin.myopenid.com/
OP-specific ID: http://matmin.myopenid.com/
5 déc. 2007 23:05:52 org.openid4java.server.RealmVerifier match
INFO: Return URL: http://localhost:8080/openid/consumer matches realm:
http://localhost:8080/openid/consumer
5 déc. 2007 23:05:52 org.openid4java.consumer.ConsumerManager verify
INFO: Verifying authentication response...
5 déc. 2007 23:05:52 org.openid4java.consumer.ConsumerManager verify
INFO: Verifying authentication response...
5 déc. 2007 23:05:53 org.openid4java.server.RealmVerifier validate
GRAVE: Discovery failed on realm: http://localhost:8080/openid/consumer
org.openid4java.discovery.yadis.YadisException: 1800: A Yadis Resource
Descriptor URL MUST be an absolute URL and it must be HTTP or HTTPS; found:
null
    at
org.openid4java.discovery.yadis.YadisResult.setXrdsLocation(YadisResult.java:111
)
    at
org.openid4java.discovery.yadis.YadisResolver.getXrds(YadisResolver.java:344)
    at
org.openid4java.discovery.yadis.YadisResolver.discover(YadisResolver.java:251)
    at org.openid4java.discovery.Discovery.rpDiscovery(Discovery.java:646)
    at org.openid4java.server.RealmVerifier.validate(RealmVerifier.java:133)
    at org.openid4java.server.RealmVerifier.validate(RealmVerifier.java:108)
    at org.openid4java.message.AuthRequest.validate(AuthRequest.java:355)
    at org.openid4java.message.AuthRequest.createAuthRequest(AuthRequest.java:101)
    at
org.openid4java.consumer.ConsumerManager.authenticate(ConsumerManager.java:1000)
    at
org.openid4java.consumer.ConsumerManager.authenticate(ConsumerManager.java:937)
    at
org.openid4java.samples.consumerservlet.ConsumerServlet.authRequest(ConsumerServ
let.java:127)
    at
org.openid4java.samples.consumerservlet.ConsumerServlet.doPost(ConsumerServlet.j
ava:96)

---- do you have any ideas?

best regards,

---mathieu minard, mminard2.ext@orange-ftgroup.com

Original issue reported on code.google.com by mathieu....@gmail.com on 5 Dec 2007 at 10:13

GoogleCodeExporter commented 8 years ago
>GRAVE: Discovery failed on realm: http://localhost:8080/openid/consumer
>org.openid4java.discovery.yadis.YadisException: 1800: A Yadis Resource
>Descriptor URL MUST be an absolute URL and it must be HTTP or HTTPS; found:
>null

This (RP discovery verification on the Consumer site) was fixed in rev391. A 
workaround doing the same can be applied like this:

RealmVerifier verifier = new RealmVerifier();
verifier.setEnforceRpId(false);
consumerManager.setRealmVerifier(verifier);

Also, you should consider publishing RP discovery, since it's a requirement 
since 
draft12 of the spec; for a quick how-to see:
http://code.google.com/p/openid4java/wiki/RelyingPartyDiscovery

Johnny

Original comment by Johnny.B...@gmail.com on 5 Dec 2007 at 10:48

GoogleCodeExporter commented 8 years ago

Original comment by Johnny.B...@gmail.com on 14 Dec 2007 at 6:03