Login Problem (O4W)
At 03 AUG 2011 02:08:14PM Jim Leong wrote:
After some work, was able to O4W to work. I was finally able to log in and was able to move around the menus.
When I followed the instructions to Create a new user, password and Persmission level, I was unable to log in. Nor was I able to log in by using the default user name a password.
Thank Jim
At 03 AUG 2011 02:20PM Dave Harmacek wrote:
You may find that the initial logon requires use of ALL CAPS in the username and password.
Dave Harmacek
Harmacek Database Systems
At 03 AUG 2011 02:43PM Jim Leong wrote:
Still cannot log in. I made sure I entered O4W and not 04W.
At 03 AUG 2011 03:30PM Dave Harmacek wrote:
The upper case situation is about the entry to the Userid and Password prompts, not the url.
Dave Harmacek
Harmacek Database Systems
At 03 AUG 2011 04:27PM bshumsky wrote:
One possible cause of what you're seeing - which I don't think was addressed prominently enough in the 9.2.1 docs, but which should be more clearly explained in the 9.3.0 release - is that each OpenInsight O4W system has a unique encryption key that, if not previously found on your system, is generated when you first run the User Management screen.
If you upgraded from a prior release of OpenInsight, you were instructed in the README to run a routine (O4WUPGRADE) which created the encryption key, and encrypted all the O4W user records; but (based on the calls and emails I've received) many users missed that step.
Even if you didn't upgrade, but instead are running O4W for the first time in 9.2.1, you had to run the O4WUPGRADE step (which will encrypt the O4W default password), otherwise when you first use the User Management screen O4W will generate the encryption key for you but NOT encrypt any existing passwords - including the default password.
Once the encryption key is set on the system, O4W will only recognize and handle the encrypted values, so any clear-text passwords will no longer work. And - since the provided, default O4W password is in clear text (if you didn't run the O4WUPGRADE process initially) - it no longer works.
Note that you can't just run the O4WUPGRADE now that the system is in this "mixed" state. The fact that the encryption key exists means that O4WUPGRADE "knows" not to try and encrypt the passwords. Instead, you must either reset your system to the clear-text state and then run O4WUPGRADE, or tell O4W to encrypt and save a new password for the O4W user.
Jim, what I suggest you do is open up OpenInsight on the desktop, log into SYSPROG, and start up the System Monitor. In the System Monitor, type in the following:
RUN RTI_O4WSETPASSWORD "NEW_PASSWORD_FOR_O4W"
where of course you'd replace NEW_PASSWORD_FOR_O4W with the new password you wanted to use for the O4W user. Note that the System Monitor WILL convert whatever you type in to upper case, so you should just save yourself some confusion by entering it in all upper case in the first place. So you might type in:
RUN RTI_O4WSETPASSWORD "O4W"
This will set the password for the O4W user back to 'O4W' - BUT it will also encrypt it so that it should work properly now.
In the 9.3 release I believe we've documented that the O4W username and password is really a "first time use" username and password, and you should (when first setting up the system) use it as the username and password ONLY ONE TIME to create a site-specific administrative username and password. This site-specific username and password will automatically be created with an encrypted password, and should work properly, while the "one time use" O4W username and password would then become invalid.
Hope that clears up some of the confusion. Please let me know if that solves the issue?
- Bryan Shumsky
At 03 AUG 2011 04:51PM Jim Leong wrote:
Bryan.. Thank You!!!
Works now. I was able to create a new user and log in with the new user or O4W