OpenID login failed I have installed the both stable and dev and both do not work, I am using pip.verisignlabs.com as the openid provider any clues?
Drupal 5.3
Configuration file Protected
Cron maintenance tasks Last run 18 min 48 sec ago
You can run cron manually.
Database schema Up to date
File system Writable (public download method)
GD library bundled (2.0.28 compatible)
JQuery Update Installed correctly
The current installed version of JQuery is 1.1.2
MySQL database 4.0.27
PHP 4.4.7
Unicode library Standard PHP
Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.
Web server Apache

Comments

mwpeters’s picture

Version: 5.x-1.x-dev » 5.x-1.0

I would just confirm this.
Since it works fine for me in the Drupal 6 beta I suspected this backport would work.
Both my provider and my account shows the registration, and the OpenID dialog all seems normal, except no login occurs and I'm taken back to the login page I stared at without achieving a change in status from visitor to the authenticated user.
I'm using an account at myopenid.com and its failing in both secure-login and regular less secure modes.
Under same conditions the log-ins are working on same server, in a sub-domain where I have the Drupal-6 beta 2 installed.

Anonymous’s picture

I'm not sure why, but pip.verisignlabs.com just does not work with this implementation of OpenID. See http://drupal.org/node/193376

I'd personally like to see Verisign's OpenID working with Drupal (is it just 5, or 6 broken on this too?), they have that browser plugin too that's bound to become popular.

Anonymous’s picture

I have the same problem here. I tested both pip.verisignlabs.com and www.myopenid.com. None of them work on my 5.5 installation.

I tested both openid-5.x-1.0.tar.gz and the current openid-5.x-1.x-dev.tar.gz. No luck.

PS: This issue looks a lot like http://drupal.org/node/174899 . They're probably dupes.

mwpeters’s picture

Problem still exists with Drupal 5.5, PHP 4.4.4, myopenid.com, etc.
No change:

  • Open ID login option presented at first use.
  • Use of Valid Open ID appears successful ... until....
  • the reloaded screen and admin screens make it obvious no recognition of valid login establishment is achieved.

    Mark

  • dynv’s picture

    Won't login ! It's on a self-managed server which works permissions and stuff automatically, I never ever had a problem with it but that may be a difference from those who have it running.

    Drupal 5.5
    Configuration file Protected
    Database schema Up to date
    File system Writable (public download method)
    MySQL database 4.1.11
    PHP 4.4.4-8+etch4
    Unicode library PHP Mbstring Extension
    Web server Apache

    suoko’s picture

    Same problem here with dev version module and myopenid.com
    I'm sure my openid's nickname works with wordpress openid plugin

    dynv’s picture

    PING ! Anyone has any connection with people involved with the module ? Can you contact them as well ? I can't wait to include it on my website !

    walkah’s picture

    Assigned: Unassigned » walkah

    Hey folks, thanks for the interest - I'm looking into this issue today and will report back w/ fixes :)

    Bricks and Clicks Marketing’s picture

    Testing this as well, using myOpenID and not having any success. Waiting patiently :-)

    mwpeters’s picture

    Version: 5.x-1.0 » 5.x-1.1

    update....
    Problem remains with version 5.x-1.1
    Never saw a problem with Drupal 6... now using Drupal 6.0 official release.
    WordPress 2.2 and 2.3 work with the OpenID plugin without problem.... Installed on same server and domain.

    softtouch’s picture

    Seems that there is no support for this module anymore?

    dynv’s picture

    Category: bug » support
    Priority: Critical » Normal

    mwpetersProblem remains with version 5.x-1.1 Never saw a problem with Drupal 6... now using Drupal 6.0 official release.

    I'm stuck with 5.x for now so a backport for it would be great !

    mwpeters’s picture

    Category: support » bug

    I think the long standing issue from this support request : http://drupal.org/node/187100

    deserves to be filed and treated as a bug report.
    That thread contains lots of information.
    The issue has the effect of making a otherwise very wonderful module, totally useless.

    greggles’s picture

    I use both the 1.0 and 1.x-dev with myopenid on several hosts with no problem, but I'm also using php5.

    Perhaps this is a php4 problem?

    JohnForsythe’s picture

    I'm using the latest build of PHP5, and can't log in with AIM, Yahoo, or with my account at myOpenID.com. I get "Sorry, that is not a valid OpenID. Please ensure you have spelled your ID correctly" or "Login Failed", depending on the ID used. But the logins work fine on other sites. If someone could post a working 5.x site with OpenID enabled, I'll try to log in, just to confirm.

    frosev’s picture

    Just like to add to this as I'm having the same problems as mentioned above

    lopolencastredealmeida’s picture

    Priority: Normal » Critical

    This also happens with Drupal 6.1 so this is not an issue just for D5.

    Same non logging with myOpenID and ClaimID and even my own hosted OpenID server based on Clamshell and/or Barnraiser's AroundMe PI.

    greggles’s picture

    Category: support » bug
    Priority: Normal » Critical

    @humaneasy - do you have any information about the host your sites are running on? PHP4? PHP5?

    duckpuppy’s picture

    Adding my case to the list of failures. I've been able to successfully add my verisign and vidoop openids to my profile on my site, but I can't log in with them. No errors, just right back at the same page not logged in. I'm running 6.2, and it didn't work for me on 6.1 either (except for the adding part). I'm running PHP 5.1 on a Linux server.

    EDIT:
    Just went to Mollom.com and was able to register using nothing but my Verisign OpenID - worked great. Still couldn't log into my site during the same session.

    Leeteq’s picture

    Subscribing.

    matute’s picture

    I have tested with blogger but it throws me:

    error:Invalid AuthRequest: 768: Invalid value for openid.ns field: http://openid.net/signon/1.0

    I'm trying with the URL: http://mbasilico.blogspot.com
    It's a Drupal 5 install, PHP5 and MySQL 5

    somebody can help me please?

    Thanks in advance

    Matias

    waddles’s picture

    Disregarding #21, which I think might be a different issue, I'm wondering if all these silent failures may be due to drupal servers being behind a proxy server. There are numerous places where the drupal server itself needs to make http requests to the openid providers using drupal_http_request().

    The long-standing #7881: Add support to drupal_http_request() for proxy servers (http not https) issue for all drupal versions < 7 has a workaround at #72 for drupal-5.x sites which should solve any proxy problems. Can anyone test that and report back whether it solved the openid failures?

    Alternatively, can somebody capture the network traffic between drupal and the provider during a failed login attempt?

    sergiopasra’s picture

    Same problem #21, drupal 6.2, mysql 5, php 5.2
    Openid login works with yahoo, but don't with blogger

    error:Invalid AuthRequest: 768: Invalid value for openid.ns field: http://openid.net/signon/1.0

    If this is a different problem, I can open a new bug report

    waddles’s picture

    techtonik’s picture

    wad, is there nobody from developers to apply patch #24 or ask me some questions if in doubt?

    greggles’s picture

    You need reviews. This is apparently a "critical" issue and yet nobody has taken the time to review it.

    Everyone who is having this problem should try to use that patch and see if it fixes it for them.

    Leeteq’s picture

    FYI: Some configurations working against Yahoo listed in this comment:
    http://drupal.org/node/378178#comment-1281250

    schuyler1d’s picture

    Status: Active » Reviewed & tested by the community

    I tested patch #24 and it works for me. (Note, applying the patch as-is to 5.x-1.3 fails to modify a comment line, but otherwise patches cleanly)

    Thanks!

    kenorb’s picture

    Issue summary: View changes
    Status: Reviewed & tested by the community » Closed (won't fix)

    After over 8 years, sounds like won't fix.