Newbie on Session State

[Guest]

Hello All!
Happy Friday, thank GOD!!!
So last night I realized I need to use Session State in my web application.
All I want to do is take the user name, and bring it back into any page I
want. I also have another web application built within my app, and I want to
be able to pull up that user name in the second web app as well.
Right now, after my user login in, they can go anywhere in my web app, but
when they jump over to the other web site, that app won't let them in. But I
thought if can carry the user info into that site, I should be good. I just
need a quick example or a good straight forward tutorial. Everything I been
finding has been just bit by bit info. I never done this, or seen it done,
so I would like to see a full simple example.

TIA!!!!

Rudy

 

[Guest]

Hello Again.

OK, I'm a idiot. I didn't see my value that was coming up on the page, need
more coffee. So now I'm getting a pretty good handle on this, now that I
finally see how it works. It just scares me on home much stuff I don't know
that I could use to make my programming task so much easier.
Anyway, I''m still working on how to pass the info in my second app, would I
use this info in my global file?

Any thought would be great!

Thanks to all, have a great weekend!

Rudy

 

[Guest]

A great way to do that is to....
1) Have a centralized Security model (e.g. Active Directory, a Single User
Database, Web Service, etc.)
2) have a single User Profile base. That could be a database, a web
service, or in the case of my company, we store the attributes inside of
Active Directory as well.

Then make all of your applications use those services.
if you have to worry about how AppX passes data to AppY, that's easy....but
when Appx, Appy, Appz and AppW all need to pass user information between
them, you have 12 possible paths for the information flow. Seperating it out
into a seperate service cleans all of that up.

 

[Guest]

Thanks David!

A great way to do that is to....
1) Have a centralized Security model (e.g. Active Directory, a Single User
Database, Web Service, etc.)
2) have a single User Profile base. That could be a database, a web
service, or in the case of my company, we store the attributes inside of
Active Directory as well.

Then make all of your applications use those services.
if you have to worry about how AppX passes data to AppY, that's easy....but
when Appx, Appy, Appz and AppW all need to pass user information between
them, you have 12 possible paths for the information flow. Seperating it out
into a seperate service cleans all of that up.