Welcome, Guest. Please Login.
05/25/25 at 12:16:10
News:
Home Help Search Login


Pages: 1
Send Topic Print
User Passwords in EVO (Read 544 times)
geo@jps
Browser
*




Posts: 39
User Passwords in EVO
04/04/06 at 06:53:51
 
All,
 
In EVO is it possible to force password changes on users such that the Admin would not be able to login as the user without the users knowledge? (Basically like Windows networking where I can reset a users password, but I don't have any way to find out what it is.)
 
Thanks,
 
George
Back to top
 
 
  IP Logged
Lynn_Pantic
Administrator
*****


evolution (n) -
gradual change to a
different form

Posts: 5663
Re: User Passwords in EVO
Reply #1 - 04/04/06 at 08:50:39
 
Not a way to force it but there is a Change Password option.  If they have someplace on the menu access to PASSWORD.INT as a change password program then they will also have File - Change Password as an option.  We will look at adding additional security.
Back to top
 
 

Lynn Pantic
IS Tech Support
lynn@istechsupport.com
Email   IP Logged
geo@jps
Browser
*




Posts: 39
Re: User Passwords in EVO
Reply #2 - 04/04/06 at 09:07:31
 
Lynn,
 
Two questions:
 
If they had that access would the user also be able to change someones password also?
 
Once the users password was changed would the Admin have any way of seeing it?
 
We're getting caught up in SOX, so we're moving into unexplored territory!
 
Thanks,
 
George
Back to top
 
 
  IP Logged
Lynn_Pantic
Administrator
*****


evolution (n) -
gradual change to a
different form

Posts: 5663
Re: User Passwords in EVO
Reply #3 - 04/04/06 at 16:08:12
 
1.  They can only change their own password.
2.  At this time the Admin can still see them all but the SOX world will make us change that I am sure.  
 
We have a number of users that, like you, are divisions of publicly held corporations and the SOX requirements are becoming a reality so we are continuing to look into ways to become compliant.  The audit trail of transactions was already added and we continue to look for ways to improve.  The reality is, DBA Classic without the Evo menu can not be made compliant because we do not have access to the login process of the menu itself.  Anybody needing to satisfy a SOX audit will need Evo and we recognize there is still more we need to do, but at least in Evo we have the ability to do it.
 
SOX SUX - Thanks, Enron...
 
Hmmm...  We have RoHS, SOX, Bioterrorism Act, ISO...  Anything else to throw into the mix?
 
Suggestions welcome.  Maybe I should start a new section for Regulation Compliance.
Back to top
 
 

Lynn Pantic
IS Tech Support
lynn@istechsupport.com
Email   IP Logged
Pages: 1
Send Topic Print