Thank you for this great module. It's working super and is exactly what we need!

After disabling certificatelogin and emptying cache (and completely disabling SSL, etc), users are unable to login. The log shows that pages are being accessed by anonymous, and I also see 15 or so instances of "certificatelogin" in system and variable db tables.

When a user tries to access a page, say "projects", they get access denied and the core login form is shown (so far so good). Enter username and password, then click Log in -- the result is a blank page with this URL in the address bar: hffp://mysite.com/certificatelogin/denied?destination=projects . No difference between admin user or normal users, browsers, etc. (I also have a residual admin login that I never logged out, so it still has the cookie/token so I'm able to change settings, etc)

By the way, this is all happening on a sandbox -- I'm disabling certificatelogin module only temporarily, just because I have a minor problem and I'm debugging. (That issue is that upon saving a node it just sits there; We also have a major problem with SSL re-negotiation requests that are causing apache to buffer huge posts (uploads), so this part of bigger rearchitecting apache+drupal)

Since there's no uninstall, should I ignore these residual values? Any advice on getting certificatelogin fully disabled?
Thanks!

Comments

mudd’s picture

Oh, and when I restart the browser and go to hffp://mysite.com, I get a drupal_set_message error:
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'certificatelogin_denied' was given in /var/www/html/includes/menu.inc on line 348.

flamingvan’s picture

Hi Mudd,
Are people really being redirected to 'hffp' or is that a typo? I am not sure why that is happening, but I don't think it's the module. It sounds like there could be a problem with the way your serever is configured, so you might start by looking into that.
Sorry there is no uninstall. The module only makes changes to the variable table, so if you wanted to completely uninstall it you could delete all the rows in that table where the field 'name' has a value that starts with "certificatelogin", but I don't think that should be necessary.
Have you tried disabling all non-core modules to see if that fixes the problem?

mudd’s picture

No, I wrote "hfft" as an intentional typo just because I expected Drupal.org to rewrite URLs telling me I'm not allowed to link (many sites do this, and well, I guess I'm trained to not try :). That has nothing to do with the question - Sorry to be confusing.

What I'm trying to do is setup drupal to use certificatelogin in concert with a management app that we wrote outside of drupal. The management app simply sets up the drupal login cookie, and allows the user to generate/submit certificate signing requests, and install private SSL certificates.

EDIT:

So, I'm not sure if this is my environment or Drupal reacting to the residual data. Have you tried disabling your module?

I just had a talk with our developer who wrote the management app, and he said he made huge changes to your module on our site. So it has to be our environment - never a dull moment!

mudd’s picture

Status: Active » Closed (fixed)