Re: Authorization code fails in Leopard
Re: Authorization code fails in Leopard
- Subject: Re: Authorization code fails in Leopard
- From: Rosyna <email@hidden>
- Date: Fri, 10 Nov 2006 08:19:26 -0700
Remember, when a password dialog is shown, it's shown by another
process (SecurityAgent in Tiger, don't remember what in Panther).
Which means all the threads in the current process are halted, the
other application is called, and the control doesn't return until the
application (SecurityAgent) gives back control to the calling
application and restarts all the threads.
So it could fail if SecurityAgent deadlocks (which I've never seen
happen, I have seen the process not be running, but that just causes
an immediate "incorrect password" to be returned to the calling app).
One possible reason for a "separate" deadlock is if the authorization
method (which is extendable) deadlocks and the actual authentication
cannot be made. I have seen this once or twice when on an extremely
flakey network and using network based authentication (which is not
default).
But then again, I am not sure if there is any way to recover from
these failures programmatically nor am I sure it's even possible to
detect these failures.
Anywho, this isn't directly related to cocoa, AFAIK.
Ack, at 11/10/06, Elango C said:
Note: If I give the wrong password to the authorization dialog; it popups
that the password is wrong, whereas the hang issue happens only when i give
correct password.
Can any one help me on this.
--
Sincerely,
Rosyna Keller
Technical Support/Carbon troll/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden