rclayh
|
| Posted: 06/05/2003, 3:54 AM |
|
IIS, C# - But would like to know how to do this in pure CCS. I have ApplicationA that uses the same database and security model as ApplicationB under ASP.NET. When you authenticate under ApplicationA and then move to ApplicationB you currently have to relogin to ApplicationB. Anyone worked out a simple way to automatically login the user for ApplicationB?
I would assume you could set a cookie (a session variable probably goes out of scope) and trigger some sort of auto-login but I'm hoping someone else has already worked it out here.
|
|
|
 |
RonB
|
| Posted: 06/05/2003, 4:46 AM |
|
1. If you can start app.B from within app.A (and vice versa)the session variable would not go out of scope. Or you could make a sepperate start screen with the option to start both and even more applications also ensuring that session variables do not go out of scope.
2. Register the session variables in a seperate database table upon login. In the startup process of your applications first check if a session has been started in a certain timeframe(the last hour for example). If yes .. use the stored variables from the table to create new session variables for that application.
Ron
|
|
|
|
rclayh
|
| Posted: 06/05/2003, 11:10 AM |
|
"Or you could make a sepperate start screen with the option to start both and even more applications also ensuring that session variables do not go out of scope."
Do that with a frameset? Or how would you do that. This seems most practical since all I need is a UserID.
Clay
|
|
|
|
RonB
|
| Posted: 06/05/2003, 4:09 PM |
|
all you need is the startpage with the links to app1 and app2. You could provide a return link to the startpage in the two apps. The actual login can be started from within the app. As long as the startpage was the origin the session variables will remain in scope. So if you started app.1 from the startpage and were to return to that startpage from within app.1 to start app.2 the session variables will be in scope.
Ron
|
|
|
|
