Custom STS with Azure AD authentication When a user tries to login, I redirect using WS-Federation to Azure AD to get the user authenticated Idea is to get the token back into my CSTS, create the user within my system if does not exist (auto-provisioning) and generate claims, merge claims and send token to the relying party the user is coming from to my CSTS acting as an R-STS
Roadmap for implementing Interfaces for Static Methods The problem isn't that statics don't support interfaces, it's that code is relying on static types when it should be relying on interfaces and instance types Static code isn't easily mockable
How to debug and run the XBAP applications? That's actually one of the advantages of xbap's deployment choice: from a user's perspective, it's pretty transparent (=no prompts, no shell presence) and, from IT perspective, relying on ClickOnce for deployment allows to easily handle which version of the xbap users run in their boxes
Method to disable keyboard and mouse I would considder to have an app that can handle all it's environment throws at it, instead of relying heavily on a predetermined setup All the "hacking" around in your system does not make it's operation more transparant The amount of work involved (to have your app block certain events) should be comparable
ID3242 The security token could not be authenticated or authorized I would make sure the certificates assigned for your claim issuer or relying party trust in the ADFS mmc are the right ones If you have not selected certificates for your these then this is probably the issue
BackgroundWorker - RunWorkerCompleted method not Firing Learn about Invoking (instead of relying on RunWorkerCompleted and ReportProgress being invoked for you) and and never forget to rethrow exceptions that happened in the thread