Hi, what's the reason for removing the authenticate to a role mechanism? I did not find any explanation except the CVS message from November 14, 2008.

Comments

jonfrancisskydiver’s picture

jonfrancisskydiver commented

The biggest reason was the Drupal caching system; specifically the menu. However, when you are authenticated as a user, the caching system isn't used. So I figured that anybody who was using the module, could just assign the roles to the ip authenticated account and you would have the same ability.

dmjossel’s picture

dmjossel commented

Except then you'd have lots of people using one user account and not using their own user accounts.

Can you at least take the phrase "authenticates an IP to a role" out of the module's title now that it doesn't do this... at all?

scotwith1t’s picture

scotwith1t
Location Birmingham, AL
commented
Title: Authenticate to a role » (does not) Authenticate to a role
Version: 6.x-1.x-dev » 6.x-1.5
Category: feature » task

I completely agree. I was misled by the title...if you can't authenticate to a role, only to a user, the title should def. be changed to "authenticates an IP or range of IPs to a user". The instructions/description should probably be modified too.

scotwith1t’s picture

scotwith1t
Location Birmingham, AL
commented
Status: Active » Fixed

title was changed and info on module summary info updated. thanks. much clearer.

Status: Fixed » Closed (fixed)

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