|
A test solution I have been working in recently at some unknown point started returning null for the Principal after LoginAsync is processed. Here are the key points of my current solution configuration:
- I have an implementation of IEntityLoginManager and it is definitely being found and called.
- The IEntityLoginManager implementation is currently returning an instance of GenericPrincipal with a GenericIdentity.
- There are no Exceptions being encountered or anything questionable being captured in DebugLog.xml.
- When LoginAsync returns to the client the Principal object is null and SessionKey value is {00000000-0000-0000-0000-000000000000}.
I've gone as far as simply executing LoginAsync on the DefaultManager from App.Application_Startup() as the very first action in the application and even in this scenario the same outcome of a null Principal is encountered. When recreating the scenario with just the key objects from the problematic solution in a new solution the Principal object is returned as expected clearly pointing to something I have specifically done wrong in the problematic solution.
Any feedback is greatly appreciated - I'd like to figure out what I have done to cause this issue so that it can be avoided in the future.
|