StrataFrame Forum » StrataFrame Application Framework - V1 » Role Based Security » User keeps going inactive

User keeps going inactive

Greg McGuffey — Mon, 26 Mar 2007 21:55:27 GMT

In my test environment, I have a test user that keeps going inactive. I activate him (Henry Helper) attempt to log on, mistype the password (not on purpose, but rather because I'm absent minded ;) ) and it says the account is inactive. I go into the security tool, and sure enough the account is inactive. I'd expect a message indicating the password is incorrect or the user name and password don't match and be allowed to try again. There must be some setting I'm not understanding.

RE: User keeps going inactive

Trent L. Taylor — Mon, 26 Mar 2007 21:55:27 GMT

Sure ;)

RE: User keeps going inactive

Greg McGuffey — Mon, 26 Mar 2007 16:19:21 GMT

OK, this time when I read these, I understand them :D Thanks!

RE: User keeps going inactive

Trent L. Taylor — Mon, 26 Mar 2007 15:31:44 GMT

Yes, this is in the documentation. An admin has to turn it back on.

Documentation Articles

Role-Based Security -> Security Maintenance -> Global Preferences -> Global Preference Properties

and

Role-Based Security -> Security within the Application -> Logon -> Failed Logins

RE: User keeps going inactive

Greg McGuffey — Mon, 26 Mar 2007 15:26:41 GMT

So, if they fail more than this number, there account becomes inactive? Is this until an admin activates them or just for a while?

RE: User keeps going inactive

Trent L. Taylor — Mon, 26 Mar 2007 15:23:14 GMT

It is in the global preferences. Open up the SecurityDialog and go to the global preferences. It is under Login Attempts.

RE: User keeps going inactive

Greg McGuffey — Mon, 26 Mar 2007 15:16:01 GMT

Not really concerned with the message, just that the user is marked inactive with a single failed login attempt. What did I setup to make this happen? There must be some way to allow a user to attempt more than a single login attempt?

RE: User keeps going inactive

Trent L. Taylor — Mon, 26 Mar 2007 14:01:08 GMT

There is no message and the message does not change. The reason for this is basically more security. By giving too informed a message in this scenario, especially when tight security is needed, it just gives one more leg-up to the person trying to get in illegally. You can adjust the time span and/or the invalid login attempts in the global preferences if this problem persists in your environment, but as of now we have no plans of changing the message.