Shane,
It took me a while to track down the likely issue with the User Manager. The key is to call UserManager.Initialize() before using the class.
The initialize method creates the internal caches used to store authenticated user information. If these caches are not enabled, a user can authenticate but the authentication state is not persisted.
Since these caches are static members of the class, you only need to call Initialize once per life cycle of the web application. A good way to prevent calling it multiple times is to store an initialized flag, such as setting HttpContext.Current.Application["UMInitialized"] = true.
That should get you over the user manager hump at least. With that out of the way I can get to preparing the invitation information for you.
-Noah
|