Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Imagine if your development team were asked to develop a system. The system should only response to some particular user groups such as "Group A", "Group B" or "Boss" who are the actually users of the system.

If you receive a phone call from the user saying that the system crash upon some particular situation/parameters. You tried to reproduce the problem and discovered that you Ip was filtered because there are not any valid user groups which include you/your team. You cannot even reproduce the crash and you go to ask the caller if you can borrow his/her PC to reproduce the problem at once.

After this, would you think adding a new valid group such as "Developers" would be necessary?

share|improve this question
up vote 2 down vote accepted

Once you start filtering by IP address, you have to configure your network to use static IP addresses. If anyone is using DHCP clients, then your whole design is useless.

In such situations, you would be better advised to use hostnames (as from DNS) instead as these will refer to the user's terminal (assuming the user only ever connects from 1 PC and is not allowed to connect from any other).

So, adding a developers group is perfectly fine design, but you need to understand that this group will change IP addresses and potentially hostnames much more often.

It would also be advisable to add a 'back door' administrative system that bypasses this security mechanism so you can debug; or ensure that you (as a debugger) can be added to the relevant user groups as needed.

You should first try to reproduce the issue with the user's configuration though, so a mechanism for copying that so your PC has the same setup as the user's would be part of a good design (as if you can only reproduce it on the user's pc, that won't help you to debug the cause) And a comprehensive system for logging all activities as the system runs would be good too - if you had that, a huge amount of errors could be determined just by looking at a log file.

share|improve this answer

We have a similar Groups set up with our client. Only instead of IP ranges, our system connects with the client's active directory to grant users access to the application. We then have a Users & Groups set up screen where groups can be given access and users can be added to groups.

In our case, the user provided us with a user that they manage. We have one prod user for all developers. When the password changes, we are sent an update email and need to keep track of it.

The site admins at first granted us access when we needed it and removed it when we didn't, but has since given the developer full access. We aren't admins, but we can access everything.

So, instead of creating a group just for your dev team, asking the client to make a user that your team can use to troubleshoot issues might be the way to go.

share|improve this answer
You will want both a 'user' account and any other type of account or at least the ability to mask the 'developer' account has those for debugging purposes within a live environment. A bug that only appears for the accounting staff and not for their supervisors without this ability would be tough to track down. – Ramhound Aug 4 '11 at 12:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.