1 Authentication
The autentication process is done in two steps.
- User validation checking user exists and it's enabled in
wic_conf
database. - Credential validation, by checking entered password is valid.
Credential validation is normally done by using the standard JDBC
realm (check against wic_conf
).
If your installation requires LDAP
or a custom authentication you can override the authentication mechanism for an
specific server.
- By setting an LDAP authentication, user credentials will be validated by LDAP.
- By setting a custom authentication, user credentials will be validated by the valve logic.
1.1 LDAP
LDAP authenticators.
wic_ldap_authenticators | |
---|---|
Label | Description |
Code | Code of the server |
Name | Name of the server |
Type | Depending on the type, the connection carried out will be different and is necessary to inform ones or the others
fields:
|
Connection URL | Connection URL, for example ldap://192.168.10.43:389 |
Connection name | Connection name, for example cn=Manager,dc=deistersoft,dc=com |
Connection password | Connection password of the indication of connection URL y connection name |
User pattern | Pattern search for the type "One level binding pattern" |
User base | User base, for example dc=deistersoft,dc=com |
User searh filter | We indicate the identifier used to look for and it will be replaced by user base |
User password field | |
Referral | When Active Directory needs to search from the domain root of active directory or need to referral, occurs the problem "PartialResultException: Unprocessed Continuation". To solve this problem needs to indicates referral at context enviroment.
For more information see jndi doc.
|
1.2 Custom valves
TO DO
This section is incomplete and will be concluded as soon as possible.wic_xsql_authenticators | |
---|---|
Label | Description |
Code | Code of the custom valve for authenticating |
Name | Name for the custom authenticator valve |
XSQL | XSQL-Script authenticatior |