Question

I’m not sure if I’ll be clear enough in my explaination to make you guys understand, but I’ll try.

Here’s my problem:

We have an external site which the users in our company connect to by giving their corresponding username and password. The external site is an ASP.NET website. We want to integrate this website into our intranet portal so that the users don’t have to enter their UN/Pwd to login to the website. Since the target website has no provision for SSO, we are simulating the POST request to login.

So far so good.

We are now required to perform an action after the initial login is done, on an another page. We can simulate the corresponding POST request as well. But the problem is since we are not maintaining any session information in our initial POST request, it always redirects to the login screen!

Is there any way to maintain ASP.NET session information between multiple calls done programmatically? Can we create an ASP.NET session id cookie programmatically and then pass it along with our initial request?

Or this is not possible at all?

Any comments are appreciated.

Thanks for your help.

Regards.

Answer 1

Maintaining the state is the responsibility of the other site (typically in a cookie).

You should perform the actions manually, then use Fiddler to compare the HTTP requests and figure out what’s wrong.