by scottgcampbell on Fri Jul 17, 2009 3:20 am
One thing that I would be concerned about would be the users can then disable themselves/others, either on purpose or by accident. Also they could disable profiles that you probably don't want to be disabled, QSYSOPR/QSECOFR/etc. I don't know what the best solution is in this case, do you have a list of allowed profiles, or disallowed profiles.
In my case it is relatively easy since all of the profiles that need to log on all start with a common prefix, so I can disallow anything that doesn't match as an invalid attempt without checking any further. But if you want most people to have access but not others you might need to do something like check the group the user profile is associated with and disallow access based on that. It also gets more complicated when you allow somewhat restricted outside access to the website, you don't want to create user profiles for everyone who needs access, unless it is a small and known group, so you will need some other mechanism for tracking the username/passwords, and validating/encrypting them, and resetting lost passwords etc (LDAP maybe?). Hopefully this might start some discussion of what others are doing to validate/invalidate what I've done and others are doing.
Scott