We are on 15.1.1.2998 release with a highly customized e-Content manager and e-Communities with the iMIS Public Views as the main website.

Previously in the 15.0.3 iMIS Public Views the unified login worked with the following logic.

Call to the function was all that was needed.

tmp = Asi.ContentManagerNet.Utilities.LoginToColdFusion(((Asi.ContentManagerNet.DisplayPageBase)this.Page).Website, decimal.Parse(GetCurrentiMISID()), PasswordBox.Text, true);

tmp returns a value something like this.......

CFID=476864; CFTOKEN=92938962; DATASOURCE=iMISUpgrd; JSESSIONID=40309e13881d101c7e; ASP.NET_SessionId=k4ohrv55whmuukig4v10w555; Login=401C6F01E4D587BB7726EDEA66E94EC21F20E1E76A6476E2BB3FAC2463EFCFB42350A56D142ECDA7C5

AB56B770B464F2E9708E25016DE1F4F846502479A5D7; UserID=j4e0T6c+CLY=; FirstName=R; LastName=Gln; FullName=R Gln; Company_ID=; Email=ri@op.org; Organization=; SecurityGroup=tROkKet0p0uPfFyiVS5jw==

When CF debugging is enabled then the tmp variable returns the

CF variables as well that indicate that the cfset FORM.Password = URL.Password is set but not maintained

(could this be a CF state/persistance issue?).

There is a CF page \AM\AMeseries\eSeriesKeepLogin.cfm that is not called from the unified login. Should it be included?

The CF variables look correct when derived from the CF debug of the tmp variable.

CF page flow for the custom unified login.ascx control that authenticates and returns a coldfusion ID and cookie values were derrrived from the CF debug output of the tmp variable..

C:\Program Files\ASI\iMIS15\iMIS_public\AM\Application.cfm</td>

C:\Program Files\ASI\iMIS15\iMIS_public\AM\ApplicationCustom.cfm</td>

C:\Program Files\ASI\iMIS15\iMIS_public\AM\ApplicationUDFs.cfm</td>

C:\Program Files\ASI\iMIS15\iMIS_public\AM\OnRequestEnd.cfm</td>

C:\Program Files\ASI\iMIS15\iMIS_public\AM\Security\LoginFromAspnet.cfm</td>

I believe that if we can propogate the ASP.net login.ascx control password and the ContactID to the CF page C:\Program Files\ASI\iMIS15\iMIS_public\AM\Security\LoginFromAspnet.cfm this may remedy the unified login issue.

When CF debugging is enabled then the tmp variable returns the CF variables as well that indicate that the cfset FORM.Password = URL.Password is set but not maintained (could this be a CF state/persistance issue?). There is a CF page \AM\AMeseries\eSeriesKeepLogin.cfm that is not called from the unified login. Should it be included?