Hi, I don't have a quick fix for you, but more a suggesion to how to proceede. Given that you don't use the AD-integrated authentication, but instead uses plain DNN you should be able to achive what you want by using a SQL-server trigger on the "aspnet_Membership" database. The trigger should be of type "AFTER-trigger", and should simply check if there is an attempt to update a given userID, and if it's a match with the userID of your "common" user, it should simply rollback the update. The userID for your user you can find in the table "aspnet_Users".

Instead of hardcoding the userID in the trigger you could of course add a new table to the database where you store the Username of you "special" account. By doing so you can achieve two things - first you can remove the "common" user by simply removing the record in the table, and second - you can have several accounts that are "locked".

If you choose to implementing such a solution you should remember that it will disable all editing of the targeted account - even from the superuser. This means that you might have to remove the trigger in order to change the password of the user. (Based on security considerations you should never keep the same password for eternity).

Finally a disclaimer: I have not tried this myself yet, therefore I will absoulutely not give any guaranty that this will work, and that it won't mess up the rest of your DNN installation (so do not try it on a production system!).

I will however test it out when I have time. I'm currently working on a custom module that will enable automatic access to the portal based on the IP-address of the request, and in that solution I will need the same functionality as you describes.

If you need more information about triggers in SQL Server you can look at http://www.sql-server-performance.com/nn_triggers.asp or simply do a google for "sql server" and "trigger".

Hope that this can help you on your way to achieve your goal.

Regards

Audun