iamhe

Hi,

I've written a Credential Provider that often takes several seconds to finish processing GetSerialization(). I'm finding that the fields on the tile (password edit field, submit button) stay enabled during this time. This is a problem; a user will invariably end up hitting submit more than once when this happens. Also, they can edit the password field before GetSerialization() returns ... definitely not good!

Does anyone know why this is What is the correct way to solve this I suppose I could disable the two fields with SetFieldInteractiveState(), but this doesn't seem like the best way.

Thank you,

-IAmHe



Re: Security for Applications in Windows Vista Credential Provider: Why do tile controls remain enabled during GetSerialization()?

standixon

Same problem here. SetFieldInteractiveState not working (READONLY and CPFIS_DISABLED are not implemented for Windows Vista) Any idea




Re: Security for Applications in Windows Vista Credential Provider: Why do tile controls remain enabled during GetSerialization()?

Poidl

It seems that there is currently no solution for this issue, we had the same problem and also contacted therefore Microsoft Technical Support ...

What we finally did is starting a thread which creates an invisible dialog which take the handle from ::GetForegroundWindow() as the parent handle. Create this Thread when entering the GetSerialization and deleting when leaving this method. This Window blocks all user input, so that it is not possible to press any Submit button again.

This is not very beautiful for the user, but it works