Authentication is the process of IDENTIFYING, and verifying, a user. The process of authentication and login can be broken down as follows:

1. Authentication INFORMATION is extracted from the request. In CQ this is done by an authentication handler.
2. The authentication information is then checked to determine whether it is sufficient and/or correct. In CQ this is performed by the login modules.
3. The appropriate response is initiated.

For CQ, initial authentication uses a standard HTML-login form in conjunction with the Authorization Header Authentication Handler. The HTML-form must have fields for the user NAME and password (the same field names must then be used by the Authorization Header Authentication Handler).

You can also use a similar form for controlled ACCESS to various areas of your website. For example, CQ can interact with a LDAP server that stores user information centrally, eliminating the need for duplication. This CENTRAL server is then used to verify login information which enables you to realize Single Sign On, both with other in-house applications and external Portals.

Authentication is the process of identifying, and verifying, a user. The process of authentication and login can be broken down as follows:

For CQ, initial authentication uses a standard HTML-login form in conjunction with the Authorization Header Authentication Handler. The HTML-form must have fields for the user name and password (the same field names must then be used by the Authorization Header Authentication Handler).

You can also use a similar form for controlled access to various areas of your website. For example, CQ can interact with a LDAP server that stores user information centrally, eliminating the need for duplication. This central server is then used to verify login information which enables you to realize Single Sign On, both with other in-house applications and external Portals.