Am aghast this morning to read of the potential issue relating to implementing strong passwords..
Why would the development team simply not code the login screen in Progression to simply use the credentials already used by the Windows operating system for the current session? We have several other apps that use this and work well and do not need to have another seperate system to maintain usernames and passwords for their application. They also include a function to login as another user.
Using the Windows Operating System to provide username and password acheives 3 things.
- Less complex
- Simple to administor
- avoids maintaining redundant username and password systems, the Windows operating system already does this so why reinvent the wheel?
I note the HOT TOPIC article throws the reponsibility back on the Network Admin. THANKS (not)! It would be nice if the author provided a link to a document that told you simply how to turn off Strong Passwords altogether. Turning off Strong Passwords until the service pack pack is released would avoid the problem all together (again another simple resolve).
Macola should step up to the plate on this one if a company runs into this problem Macola should take the call and assist with the resolve free of charge, not tell the company to call a support provider.
How could anyone miss this problem in testing? Is anyone listening to the posts in this group?
The administrator has disabled public write access.