We installed this module and activated it for only administrators. When non-admin users log in for the first time, they see the following...

Undefined propery

Currently, our permissions set up is as follows:

  • Admins must use Duo
  • Authenticated users don't need to

Permissions

In more testing, this only seems to happen on the first time someone logs in. Subsequent logins don't produce this Notice.

CommentFileSizeAuthor
#7 undefined_property_name-2697897-7.patch666 bytescatapipper
#6 accountsettings3.png125.93 KBDocVeg
#6 accountsettings2.png87.95 KBDocVeg
#6 accountsettings1.png75.45 KBDocVeg
#2 Screenshot from 2016-03-31 13-35-45.png13.64 KBrgchi
Screenshot from 2016-03-31 12-54-35.png16.77 KBrgchi

Comments

rgchi created an issue. See original summary.

rgchi’s picture

rgchi commented
Issue summary: View changes
StatusFileSize
new Screenshot from 2016-03-31 13-35-45.png13.64 KB
rgchi’s picture

rgchi commented
Issue summary: View changes
DocVeg’s picture

DocVeg commented

I do have exactly the same settings and do receive exactly the same error messages.

The configuration was exactly done as mentioned here: https://duo.com/docs/drupal

Login with Duo (as administrators) works well and also login without Duo (as regular users) works well on my Drupal platform.

The error message above appears not during login, it appears during registration as a new user.

rgchi’s picture

rgchi commented

@DocVeg: Yes, this happens on any *new* user. After an initial login, then whatever field is populated and everything seems okay.

Our workaround: We tell people to login initially. This puts them into the authenticated role, which has equal privs as the Anonymous Role. Next, after we notice their login, only then do we promote them to a more privileged role (that also requires Duo to process for their log in). Not perfect for a large user base but it works until a patch is submitted.

Side note: We use OpenAM (transitioning from LDAP); so, we really don't have blanket user registration. So I can't speak exactly to that.

DocVeg’s picture

DocVeg commented
StatusFileSize
new accountsettings1.png75.45 KB
new accountsettings2.png87.95 KB
new accountsettings3.png125.93 KB

Didn't understand, why it is not possible to stop displaying that error message if it seems to be a issue of access rights. But if it appears at the end of the registration process of new users, they will think "that is not a safe and proper website, if already during registration error messages are appearing".
Attached are my settings - account (in German, but you can see what is switched on and off) - maybe it helps to identify the problem.

catapipper’s picture

catapipper
she / they
commented
StatusFileSize
new undefined_property_name-2697897-7.patch666 bytes

I could not get the notice to show up on the main login page but did notice it showing in the error logs. Noticed that the variables were being checked to see if they were correct without checking to see if they exist so thus I added a simple isset() around the variables and no errors anymore. Haven't seen any adverse effects either for creating a new user as admin.

Forgot to say that this is based on the 1.10 version of Duo.

catapipper’s picture

catapipper
she / they
commented
Status: Active » Needs review
DocVeg’s picture

DocVeg commented
Status: Needs review » Fixed

Hi Catapipper
You are great, your fix solved the problem. The error message don't appear any more.
Thanks a lot!
Duo wasn't able to fix it, but hopefully they will integrate it into the distribution of the Duo module for Drupal!
Best regards!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.