emonarafat / socialauth-net

Automatically exported from code.google.com/p/socialauth-net
0 stars 0 forks source link

possible to use multiple login pages #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
we are using SocialAuth.net along with forms authentication.
my question is: is it possible to have multiple login pages?
can we for example have /login.aspx as well as default.aspx as login pages? is 
there any special web.config settings we have to add?

thank you,

Original issue reported on code.google.com by ma...@techknowledge.ae on 22 Apr 2012 at 3:20

GoogleCodeExporter commented 9 years ago
Ok, this is the scenario. we have a login page /login.aspx and a default.aspx
on both pages we have imagebutton that run the code for socialauth.net (just a 
new user.login(provider, callback function)
from the login.aspx it is working fine and redirecting to the home page 
(default.aspx)
from the default.aspx, it is throwing an exception. the line that's causing the 
error is simply session("UserId") = somenumber

here is the exception details:

Server Error in '/' Application.
Session state can only be used when enableSessionState is set to true, either 
in a configuration file or in the Page directive. Please also make sure that 
System.Web.SessionStateModule or a custom session state module is included in 
the <configuration>\<system.web>\<httpModules> section in the application 
configuration.
Description: An unhandled exception occurred during the execution of the 
current web request. Please review the stack trace for more information about 
the error and where it originated in the code.

Exception Details: System.Web.HttpException: Session state can only be used 
when enableSessionState is set to true, either in a configuration file or in 
the Page directive. Please also make sure that System.Web.SessionStateModule or 
a custom session state module is included in the 
<configuration>\<system.web>\<httpModules> section in the application 
configuration.

Source Error:

The source code that generated this unhandled exception can only be shown when 
compiled in debug mode. To enable this, please follow one of the below steps, 
then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the 
error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application 
to be compiled in debug mode. The first technique will cause only that 
particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance 
overhead. You should make sure that an application has debugging disabled 
before deploying into production scenario.

Stack Trace:

[HttpException (0x80004005): Session state can only be used when 
enableSessionState is set to true, either in a configuration file or in the 
Page directive. Please also make sure that System.Web.SessionStateModule or a 
custom session state module is included in the 
<configuration>\<system.web>\<httpModules> section in the application 
configuration.]
   System.Web.UI.Page.get_Session() +2819820
   _Default.TrackLogin() +109
   Brickred.SocialAuth.NET.Core.SessionManager.ExecuteCallback() +53
   Brickred.SocialAuth.NET.Core.BusinessObjects.SocialAuthUser.OnAuthneticationProcessCompleted(Boolean isSuccess) +565
   Brickred.SocialAuth.NET.Core.OAuth1_0a.LoginCallback(QueryParameters responseCollection, Action`1 AuthenticationCompletionHandler) +105
   Brickred.SocialAuth.NET.Core.Provider.LoginCallback(QueryParameters responseCollection, Action`1 AuthenticationHandler) +57
   Brickred.SocialAuth.NET.Core.BusinessObjects.SocialAuthUser.LoginCallback(String response) +153
   Brickred.SocialAuth.NET.Core.CallbackHandler.ProcessRequest(HttpContext context) +950
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Original comment by ma...@techknowledge.ae on 23 Apr 2012 at 11:52

GoogleCodeExporter commented 9 years ago
Please refer http://code.google.com/p/socialauth-net/issues/detail?id=50#c2. 
Let us know if this helps.
Deepak

Original comment by daggar...@brickred.com on 6 Sep 2012 at 10:53

GoogleCodeExporter commented 9 years ago
Hi,

Is your problem resolved? In event of no reply, we'll assume it is either 
resolved or the help is no longer required.

thanks
Deepak

Original comment by deepakag...@gmail.com on 15 Oct 2012 at 5:31

GoogleCodeExporter commented 9 years ago
Hi,

I'm closing this issue on account of no reply. We assume either your problem is 
resolved or you're not looking for a fix anymore. If this is not the case, 
please feel free to re-open it with more details.

Deepak

Original comment by deepak.a...@3pillarglobal.com on 31 Oct 2012 at 1:01