I know this module isn't under active development according to the project page, but I will just throw this out there.

I want to have users be able to access content by entering their library card number. I don't need authentication against a database, just a regular expression pattern match. This is something I use for user registration via the private number module.

Would this be possible? If there would be interest, I would be willing to look at the code and work on a solution (fair warning: I haven't done any D7 module development, just a little in d6)

mrweaver

Comments

Grimreaper’s picture

Hello,

The feature is interesting me, only to train me to dev.

But it is a big work to do I think, seeing how the module is made.

Because there is protection to three levels.
global password
global password per content type
password on node

To be the most flexible, the validation with regex needs also to be on the three levels too but we need to provide a way to choose if it is a regex or a classic password which is active on each level.

Big work, interesting but big. I will try to do it.

Maybe decomposing in three parts, with intermediate validation by the community.

Which level do you prefer I start with ? I think I will start with the global password.

DamienMcKenna’s picture

Issue summary: View changes

Maybe just provide hooks to allow another module to extend the validation logic? Or maybe a checkbox to indicate whether a regex is used?

Grimreaper’s picture

Project: Protected Node » Entity Access Password
Version: 7.x-1.x-dev » 1.0.x-dev
Component: Miscellaneous » Code
Assigned: Unassigned » Grimreaper

Change the password validator service into a chained service so people can add their own validator before.

Grimreaper’s picture

Title: validate with regexp » Make password validation extensible

  • Grimreaper committed e228a2d on 1.0.x
    Issue #2044935 by Grimreaper, DamienMcKenna, mattrweaver: Make password...
Grimreaper’s picture

Assigned: Grimreaper » Unassigned
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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