I'm not an admin or a security guy, but this seems risky. If you write a stored process to hand-roll the process of updating passwords, you could easily end up with passwords ending up in clear text log files, etc.
I assumed most servers were set up to integrate with an independent, dedicated account/password management system (e.g. active directory on Windows), where I would assume any processes for updating passwords would be secure by design.
(Oh, I just googled. The definition of these internal accounts (@saspw) is that they exist only in metadata, not in an external authentication domain. So I can how if you've got a lot of these, you would want some automated way for users to be able to maintain them. yikes. Assuming these users only have read access to reports that aren't sensitive, maybe the benefits of having an automated stored process to allow users to manage their passwords are worth the security risks.)
BASUG is hosting
free webinars Next up:
Don Henderson presenting on using hash functions (not hash tables!) to segment data on June 12. Register now at the Boston Area SAS Users Group event page:
https://www.basug.org/events.