Our development server was upgraded to 6.5.1 at the end of last month. Since that time, when I try to click on a link that requires password authentication over the web, it prompts me 3 times and gives me our password error message.
I created new copies of the databases yesterday and all was fine during the day. When I came back in this AM, I get the same password prompts.
The link to open the secure part of the database is a hotspot that opens the Admin frameset. This has always worked in R-5. This is what it returns:
http://devserver/ph/packing/gphome.nsf/gpadmin?OpenFrameSet
The database on the dev server has an ODS of 43 so it has been upgraded.
The ACL on the Dev server has Default as Editor (No Access on Prod) and Anonymous as Author (same on Prod). I have full Manager rights & all roles in Dev.
Why can’t I log onto the secure site? Why won’t it accept my password? Is there something that runs over night that changes the database? Why would it work all day yesterday and then not work this morning? What am I missing? What’s different with ND6?
Subject: Server Upgraded to 6 - Now Password Doesn’t Work on Web
The password security has been inproved in R6.As far I could find out, it seems that you cannot have any known surname or firstname in the password. You can have surname or firstname (not necessarily the surname and firstname of the username, but any well known name) in the password if the password also contains many other characters.
In R6 also the internet shortname doesn’t always work if it’s too short or contains parts of the password or username. However in R6 you can enter just the firstname as username in most cases, and if that doesn’t work you can enter the firstname and lastname as username.
The time when a changed password comes active is much longer than in R5 though. The fastest you can get is around 2 minutes, while in R5 you could experience the password change in 20-30 seconds.
Subject: RE: Server Upgraded to 6 - Now Password Doesn’t Work on Web
Thanks for the response. I’ll keep all that in mind.
Our problem seems to be with the server. Our admins finally bounced it and everything is working now!