Running into a problem where a username token is used to
authenticate/encrypt a message to a web service. a custom token manager
looks up the password (token was configured to SendNone) in a database. this
all works fine. however if the user then goes and changes that password then
re-tries the request the server has the old token cached. I can't find how
to reset this or have some method called in my custom username token manager
so i can check if passwords have changed. the only thing we've found to work
is if the IIS cache is flushed after the database password update, then WSE
will call my username token manager so i can query the database for the
password.
Questions are:
Does anyone know how to programmatically flush the IIS cache?
Does anyone know how to force WSE to call my username token manager?
Is there some way that I can re-set the WSE token caceh so that my username
token manager is called?

Thanks,
Kyle Brandon