Recently updated to the latest dev version and now I'm repeatedly asked to enter my username & password, despite knowing that what I'm entering is verified & correct.
I've tried uninstalling & reinstalling Shield. I've also tried adding the necessary line to my .htaccess file as described in various issues and now the project description page. Neither fixed the issue.
I'm running Drupal 7.23. My local environment seems to be OK, it's just my remote Dev environment that is experiencing the problem.
I'm not particularly up on CGI etc so if anyone can suggest how I might easily provide more details about my Dev environment then please chime in. As far as I know, I've not got anything set up in a particularly strange way.
For now, my only choice is to have Shield disabled (thank you Drush!).
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | shield_7.x-1.2_-_7.x-1.x.diff | 12.01 KB | kalman.hosszu |
Comments
Comment #1
patoshi commentedi have the same issue. keeps asking for username/pass. downloaded the latest dev release.
***
ok got it working by using the 2012 version instead.
Comment #2
dddbbb commentedMy issue seems to only occur when updating from an older version of shield. Just installed latest dev on a fresh D7 site and it seems fine.
Comment #3
kalman.hosszu commented@danbohea thanks for the bug report, it's very important to test the update script so I will check it.
Comment #4
tomb-2 commentedThis is an issue on 6.x-1.1 too,
After entering a username and password the success message also requests a username and password, and will not allow you access.
Installing this module completely breaks the site.
Edit: This was a fresh install of the module.
Comment #5
kalman.hosszu commentedUpdate functions won't have critical status. If you have a problem with 6.x-1.1, open an issue in the queue with the details.
Comment #6
alan d. commentedLatest dev version, first time install on GoDaddy. And we were instantly was locked out.
Since the site was 100% blocked until setting the $config variables in the settings.php file or to disabled via the db, this is a critical issue for non-developers!
Replaced with the latest version and no issues :)
Comment #7
kalman.hosszu commentedComment #8
alan d. commentedIt killed the site for all users! How can this not be a critical issue?
https://www.drupal.org/node/45111
"Critical bugs include those that: Render a system unusable and have no workaround."
Comment #9
kalman.hosszu commentedDear Alan D! This issue it not about the stable version but the development snapshot, so you should not use it for production sites. Anyway, this is an important issue because I have to solve the update process.
Comment #10
alan d. commentedI'm simply pointing out how most people read the issues queues.
The issue queues reflect the state of the latest dev snapshot, not the state of the module when it was last tagged and released in 2012.
So skimming the issue queue, there are 0 critical and 0 major issues reported against Shield 7.x-1.x branch.
Sweet, that's a million times better than 98% of the other modules in my install. That means the worst reported bug that dev would have is a "self-contained bug that does not impact the overall functionality of the software".
But as an aside, big thanks for your work here. This module has saved multiple core hacks that would have been otherwise needed for all of our test sites :)
Comment #11
xtfer commentedPossibly related: #2382243: FastCGI param selection is not always correct
Comment #12
kalman.hosszu commentedI tested again the update in a fresh d7 installation with apache and I couldn't reproduce the issue. Could anyone test it with a CGI system?
Comment #13
cola commentedsame problem, we installed right now a brand new drupal7 with the latest dev from 2015-Jan-17.
we enabled the module, setup a username and password and press then the save button.
after that we became the login form, type the username and passwort they we defined but cannot login.
then i download the stable version 1.2 and with this version it works.
Comment #14
kalman.hosszu commented@cola would you write your environment's details? Do you use CGI?
Comment #15
cola commentedthank your kalman for writing back.
i try it right now again with a clean latest drupal 7 installation and your build shield-7.x-1.x-dev.
i setup your shield with the following configuration
Enable shield module
Allow command line access
Remote address key: REMOTE_ADDR (I also try with the other parameter)
Shield all except the following paths (exclude)
User: test
Passwort: test
Authentication mesage: hi user
our system
FreeBSD 9.3-RELEASE-p6 FreeBSD 9.3-RELEASE-p6 #1 r275703M: Fri Dec 12 17:11:45 CET 2014
PHP Version 5.5.20
Server API CGI/FastCGI
did you need some other information?
Comment #16
kalman.hosszu commented@cola thanks for the details, it's very helpful! So this problem is available only in CGI systems.
Anyone has experience with CGI environments who could help to fix this problem?
Comment #17
cola commentedthe stable version of your module (7.x-1.2) works fine with cgi. only the dev version dosent works... so it must be a change since version 1.2...
Comment #18
kalman.hosszu commentedyes it's true, we have some modifications in the module since the last stable version. The diff file is attached
Comment #19
cscott5288 commented*sigh*
This issue is happening on the production version 7.x-1.2.
This is what you get for taking shortcuts in life. Should have just written two lines in the htaccess file instead of installing this garbage.
Comment #20
geek-merlinI'm guessing this is one of the related issues. Please open a new one if not and relate to this.
Comment #21
geek-merlin