I have observed that DNN does not allow changing Role Names for Roles once created through the User Interface.

When I studied the underlying Stored Procedure, I observed that neither does the procedure supports so.

Is there any specific reason to disallow changing Role Names (Role Group Names are allowed to be changed however!!!)

For some reason, my modules require chaging Role Names after they have been created. Although I have coded the Sql & VB part of it (which was not very difficult), is there any kind of security or integration issue with the rest of DNN framework, if I am doing so through a custom module???

Then, there are 3 points I would like to know here:

1) What mechanism is used when someone selets "Remember Login"?

2) How can I configure DNN not to use cookies to persist security/permissions?

3) Even if DNN uses cookies to persist security information, how can I make DNN to reject all cookies & set them anew by asking the user to re-login after I have updated role names??? This should not be much of a problem, as obviously role names are not updated that often. However, if & when they do, it is important to expire all cookies, or else an unauthorized user may gain access to a restricted portion of the site, if the Role Names clash in some way after updation!!!

I saw a table UsersOnline that is used by DNN. If I clear that table after Role Updation, would that Logout all users???

How does DNN decide which users are logged in when it shows the appropriate icon on Admin User Management Page. If there is a IsOnline value somewhere in the DB, I can clear that. Or Else, I can clear out the UsersOnline table. Would that resolve the issue???

Can I hook into the DNN Login procedure. That way, after I update a Role, I can set some Flag myself, & clear the cookies if that flag is set, thus requiring users to relogin after Role Updation???