HttpContext.Current.Request.IsAuthenticated in an Authentication Plugin is never authenticated

Working on updating an authentication plugin. With our third party auth mechanish, HttpContext.Current.Request.IsAuthenticated gets set. This value seems to be always "false" when inside the Authentication plugin, but when I make the call from a widget extension, it works as expected. Any ideas why this would not be set at that point in the flow?

Parents

0 Ben Tiedt 5 months ago

IAuthenticationPlugin (from version 8), is called during HttpApplication.AuthenticateRequest and is expected to set HttpContext.Current.User.Identity.Name to the Community user name.

When does your third party auth mechanism initialize? Could it also be during HttpApplication.AuthenticateRequest?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Luke R Davidson 4 months ago in reply to Ben Tiedt

Seems like that is the case. Would there be an issue setting the user in the .NET PostAuthenticateRequest event ?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Ben Tiedt 4 months ago in reply to Luke R Davidson

Telligent Community needs to the user set in AuthenticateRequest -- that's what identifies the user within the Community. If its set after AuthenticateRequest, the user would likely be identified in Community as anonymous.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 Ben Tiedt 4 months ago in reply to Luke R Davidson

Telligent Community needs to the user set in AuthenticateRequest -- that's what identifies the user within the Community. If its set after AuthenticateRequest, the user would likely be identified in Community as anonymous.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

No Data