Providing Credential without login screen

[TJO]

Can someone advise about feasibility of passing user credentials to an
asp.net 2.0 application using query string or other techniques? I
want to avoid the login screen.

Thank you.

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

It all depends on what kind of application, where it is hosted (e.g. an
internal company intranet or on the public internet, for example) and how
secure you need your application to be.
Certainly if you used forms authentication with cookie persistence, there is
no reason for the returning user to have to "login" after the first time if
the persisitence expiration is set long enough.

On an intranet, Windows Authentication should be completely transparent as
the browser sends the logged on user's credentials automatically.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"TJO" wrote:

Can someone advise about feasibility of passing user credentials to an
asp.net 2.0 application using query string or other techniques? I
want to avoid the login screen.

Thank you.

[Alexey Smirnov]

On May 4, 7:57 pm, Peter Bromberg [C# MVP]
<pbromb...@yaho o.yabbadabbadoo .comwrote:

On an intranet, Windows Authentication should be completely transparent as
the browser sends the logged on user's credentials automatically.

Actually, it depends on settings:

IE - Int.Options - Security...
FireFox - about:config network.automat ic-ntlm-auth.trusted-uris

[TJO]

On May 4, 10:57 am, Peter Bromberg [C# MVP]
<pbromb...@yaho o.yabbadabbadoo .comwrote:

It all depends on what kind of application, where it is hosted (e.g. an
internal company intranet or on the public internet, for example) and how
secure you need your application to be.
Certainly if you used forms authentication with cookie persistence, there is
no reason for the returning user to have to "login" after the first time if
the persisitence expiration is set long enough.

On an intranet, Windows Authentication should be completely transparent as
the browser sends the logged on user's credentials automatically.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

"TJO" wrote:

Can someone advise about feasibility of passing user credentials to an
asp.net 2.0 application using query string or other techniques? I
want to avoid the login screen.

Thank you.

In this situation, both sites are public web applications. One on my
clients domain and one on mine.

[Alexey Smirnov]

On May 5, 4:03 pm, TJO <TimothyOd...@g mail.comwrote:

On May 4, 10:57 am, Peter Bromberg [C# MVP]

<pbromb...@yaho o.yabbadabbadoo .comwrote:

It all depends on what kind of application, where it is hosted (e.g. an
internal company intranet or on the public internet, for example) and how
secure you need your application to be.
Certainly if you used forms authentication with cookie persistence, there is
no reason for the returning user to have to "login" after the first time if
the persisitence expiration is set long enough.

On an intranet, Windows Authentication should be completely transparent as
the browser sends the logged on user's credentials automatically.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net

"TJO" wrote:

Can someone advise about feasibility of passing user credentials to an
asp.net 2.0 application using query string or other techniques? I
want to avoid the login screen.

Thank you.

In this situation, both sites are public web applications. One on my
clients domain and one on mine.- Hide quoted text -

- Show quoted text -

Does it means you would have a two login pages against two databases?

Anyway, I think the technique (it's called Single Sign-On) could be
similar to the following example:

http://blah.winsmarts.com/2006/05/19...rship-api.aspx

Hope it helps