I have a client who wants to add a second layer of security on a couple specific pages. The reason is they have given out an admin user to different people. I am now changing that as i have recently taken over the site, but he wants to make sure that even if the new login is given out by mistake there is a second password on these two pages. Is there a module available or does someone know of a way to achieve this so that even when DNN allows a user to view these two pages it will prompt them for a password?

Not exacty but I think you could perhaps achieve the goal by creating a new security role and only give that security role access to the pages.

Use an RSVP code for the security role and provide that to the users you want to be able to view the content.

They would not be challenged at the page level quite as you describe, but would have to subscribe to the role to be able to get to the page and any other content reserved for that role.

Once they have subscribed to the role, though, they are in and won't be challenged again unless they are removed from the role.

Which will be nicer from their perspective.

When they lose favor, remove them from the role and change the RSVP code for the role, and they are out in the cold.

---

pmgerholdt

Create new logins for the subcontractors, and give the subcontractors the credentials to those new logins. Put them in a subcontractor role and control what they have access to.

Then change the passwords on the existing accounts so the subcontractors can't use them anymore.

Simplest solution.

Giving out the credentials to their accouts to subcontractors was a bad idea. Solving the problem by continuing to share those accounts with subcontractors and creating a second layer of password protection for certain content is also a bad idea.

Do away with the human factor? ... Remove your client from the idea-generating and decision-making queue as a start.

Use credentials as they are intended to be used.

---

pmgerholdt