Difference between revisions of "Windows Authentication In A Web Application"

From PresenceWiki
Jump to: navigation, search
Line 1: Line 1:
 
{{Tutorials}}
 
{{Tutorials}}
  
This document describes the processes needed to Autenticate a user accessing your pages using
+
This document describes the processes needed to Autenticate a user accessing your pages by using
 
their windows username and password.
 
their windows username and password.
  
Line 9: Line 9:
  
 
  The user can use their windows username and password.
 
  The user can use their windows username and password.
The username is stored against the ip address, so that it will only need to be entered once for a machine.
 
 
  The httpsession variable is used so that the user only needs to login once.
 
  The httpsession variable is used so that the user only needs to login once.
 +
The username is stored against the ip address, so that it will only need to be entered once for a machine.
 
  A session will automatically expire when no new requests have been made for a set time.
 
  A session will automatically expire when no new requests have been made for a set time.
 
  
 
You can download the tasks for this example from:-
 
You can download the tasks for this example from:-
 
http://www.international-presence.com/wikidocs/samples/On_Demand_Windows_Login.xml
 
http://www.international-presence.com/wikidocs/samples/On_Demand_Windows_Login.xml
 +
 +
 +
To embed the task, we just place the "Check Login Sub Task" before our normal ondemand task page.
 +
It might be that all ondemand pages start from one single task,
 +
in which case we would place the "Check Login Sub Task" at the start of that task.
 +
 +
  
 
http://www.international-presence.com/images/docs/userlogin/userlogin.png
 
http://www.international-presence.com/images/docs/userlogin/userlogin.png

Revision as of 09:48, 23 August 2010

Tutorial Pages > Windows Authentication In A Web Application

This document describes the processes needed to Autenticate a user accessing your pages by using their windows username and password.

This will then also enable you to track users through the site, so for instance, if they press a button on the site to action an event, you'll be able to log who actioned the event.

The advantages of this are that:-

The user can use their windows username and password.
The httpsession variable is used so that the user only needs to login once.
The username is stored against the ip address, so that it will only need to be entered once for a machine.
A session will automatically expire when no new requests have been made for a set time.

You can download the tasks for this example from:- http://www.international-presence.com/wikidocs/samples/On_Demand_Windows_Login.xml


To embed the task, we just place the "Check Login Sub Task" before our normal ondemand task page. It might be that all ondemand pages start from one single task, in which case we would place the "Check Login Sub Task" at the start of that task.


http://www.international-presence.com/images/docs/userlogin/userlogin.png

http://www.international-presence.com/images/docs/userlogin/pleaseenterapassword.png

http://www.international-presence.com/images/docs/userlogin/usernamepasswordincorrect.png

http://www.international-presence.com/images/docs/userlogin/usernamenotfound.png

http://www.international-presence.com/images/docs/userlogin/tasks.png

Simple Task To Confirm Action

Instructions

Session Expiry

Check Login Sub Task

Login

Check User Exists in LDAP

http://www.international-presence.com/images/docs/userlogin/queued.png

http://www.international-presence.com/images/docs/userlogin/ondemand.png