Your requirement of notifying all connected clients of the outcome
of an Access-Check call that may or may not happen is bizzare to say the
Cound you do it the other way around ?
Each RPC client uses Dynamic-Tracking, and, you do the access-check
on the new resource at the next call coming in ?
It look to me that you are trying to solve the main problem of static
by building a too complicated mechanism of `re-authentication`.
Also, I don't understand your comment regarding the protocol-sequence and
In the simplest world, if you have Dynamic Identity tracking, you can always
call RpcImpersonateClient, perfrom the access check, and call-it-a-day.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at