Project:ipAuthenticator
Version:6.x-1.5
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

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

#1

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.

#2

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?

#3

Title:Authenticate to a role» (does not) Authenticate to a role
Version:6.x-1.x-dev» 6.x-1.5
Category:feature request» 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.

#4

Status:active» fixed

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

#5

Status:fixed» closed (fixed)

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