The iMIS .Net authentication is performing as expected but something has changed in how the iMIS Web Application starts the Communities Cold Fusion part of the Web Application.

Previously the function call to Asi.ContentManagerNet.Utilities.LoginToColdFusion was all that was needed to establish a cold fusion authenticated session with the .net unified login. 

Currently I am testing some variations of starting an authenticated Cold Fusion eCommunities session within the .net authentication process. This testing has met with some success but not the consistency needed.

These are set to false after the ASP.net login.

<cfif parameterexists(client.pword) is "YES" and parameterexists(client.id) is "YES"

 /iMISPublic/source/Communities/UserHomePage.cfm?Section=My_Communities

iMISpublic/AM/Template.cfm?Section=Home&template=/Security/Login.cfm

Debugging reveals that the CF Login returns a seemingly authenticated Cold Fusion eCommunities login. This is not true as we have seen.

 To solve the unified login we may simply need to pass Parameter #1(CF_SQL_VARCHAR) = 3730745 to the in \ASI\iMIS15\iMIS_public\Source\Security\Security_Filters.cfm file.