WEB>ACCESS

1. WEB>ACCESS Fast Training | Ex-Sight.Com

2. Web>Access™ allows fast & secured 1:1 recognition using face recognition algorithm through HTTP/S networks. It locally extracts the user face templates, encrypt them and deliver to the server for matching. The server matches the user identity with pre-stored registration details based on Face + Username + Password. > Overview

3. Client Side: Based on .Net 2.0 Platform Requires 640X480 Pixels Webcam Based on Microsoft ClickOnce™ Technology, Independent, External to Web-Browser Unlimited No. Of users per PC > Technical Info >>Client Side

4. Server Side: Based on Microsoft ASP.Net 2.0 IIS WebServer Virtually Unlimited No. of Users per Server ODBC Database Connectivity to any database Can be integrated into Linux Based servers using DB bridge > Technical Info >>Server Side

5. Open Database Connectivity (ODBC) provides a standard software API method for using database management systems (DBMS).Supported Database:Oracle, DB2, Microsoft SQL Server, Sybase, Pervasive SQL, IBM Lotus Domino, MySQL, PostgreSQL, and desktop database products such as FileMaker, and Microsoft Access. > ODBC Advantages

6. The user’s first registration is done by the administrator. A unique Username and Password is entered into the Users Database on the server side. > 1st Registration Create Username Password Add New User Server Users Database

7. Then the user is allowed to enroll himself into the system using his own webcam. > 1st Enrollment User Name + Password Save Face Templates 1st Enrollment X 6 Client Server Users Database 6 Face Templates

8. Web>Access™ will acquire 6 different poses of the subject for perfect Enrollment. > 1st Enrollment Move Right/Left Move Up/Down

9. Web>Access™ will acquire 2 different templates of the subject for perfect match. > Verification <

10. > Architecture Activity LOG User Name + Password HTTP Request > 256bit Encrypted Information Match < HTTP Responses Client Server Server Server Server << Wizard Steps <<< Creation of Login Cookie Face Template Users Database Users Database Login Cookie Cookies DB

11. Every user attempt to Login into server, whether it is successful or not will be audited into the Activity Log Table in the server. > Activity Log Activity LOG

12. Web>Access™ uses internal 256bit Encryption mechanism, which can easily wrapped by additional SSL/HTTPS encryption mechanism. Dynamic encryption allows highly secured communication with limited life server side Login Cookie. > Encryption #@$ Activity LOG SSL Encryption Internal 256bit Encryption

13. Client Clicks Login Button on Server HTML Page Client’s IE auto loads latest Web>Access Version from server First Time users : Auto Download 2nd time users : Auto run from local HDD > Flow Scenario >> Download

14. The user need to provide valid user name and password. After clicking “Next” the server verifies Username and Password, if they are OK the Web>Access™ moves to “Biometric Acquisition”. Invalid Username / Password will erase the typed info with an alert message box. > Flow Scenario >> Login

15. Web>Access™ will acquire 2 face templates, encrypt and will deliver them to the server for validation. The server will match the Username, Password and Face Template. >> Biometric Acquisition

16. Client Side Flow

17. Web>Access™ server will verify Username, Password and Face Templates. If the verification succeeded the server will generate a unique id that will be written to the client’s PC as a cookie. This cookie will expire automatically after 1 min, if no activity on server side. >> Server Verification

18. Web>Access™ server handles Face Ageing using Ageing+ algorithm. The algorithm relearns new face templates as a parameter of time. The relearning procedure is done due to server administrator tuning. >> Face Ageing

19. Web>Access™ server does not limit the number of Templates Per User. More Templates == More Accuracy >> Templates