BaltACD Just our normal Kalmbach IT yearly fiasco.
Just our normal Kalmbach IT yearly fiasco.
At least it wasn't the same level as what happened to Twitter yesterday.
I have an odd problem.
I normally use Microsoft Edge as a browser. Normally my password is recorded and I'm logged in automatically. Now I'm not logged in and if I try to log in I just get returned to the not logged in page. I tried manually changing my password, but got a letter case wrong and was told my login details were wrong. When I correctted it I was just back to the not logged in page.
So my password was correct, Edge just can't log me in.
As you will have observed, I'm logged in. I can log in manually on Explorer.
How can one Microsoft browser work and not the other?
Any ideas?
Peter
They handle cookies differently.
Renember that the 'session cookie' has to identify you securely across multiple accesses, but without mistakenly permitting you 'in' when your access has been revoked. Periodically any good organization will cancel persistent logins ... the time being related to security. If you responded to the FRA employment opportunity, for example, only half an hour without 'traffic' from you results in your being kicked off.
Note that in the 'good old days' this could be done by physically setting something in your "client software" -- actually deleting cookies that are good no more. In our modern age of entitlement, applications can set cookies, but not delete them; what happens instead is that the internal recognition is changed.
Now, a well-written application would check to see if key cookies were set and give a user the option to overwrite them. In the 'Alan Kay' model of security (where the most "secure" systems are those you don't know exist, let alone are using) this would be innocently framed in terms of something like 'reset Kalmbach access permissions' -- note that this would be browser-specific, as the cookies or data to be reset would be, and you would have to do this each time you used a different browser you'd logged into under the old login.
Now the 'old' version of persistent login worked across platforms: I believe this is now treated as a 'security hole' by some modern browsers much as using straight http:// instead of https is.
In short, going into Edge settings, deleting all the Kalmbach set cookies, and flushing the cache and saved pages should definitively fix this and future repetitions. As I don't use any machines that run Edge I can't give you detailed instructions, but others have done that.
Our community is FREE to join. To participate you must either login or register for an account.