Starting with version 0.4.4 (revision 4), the AuditConsole provides additional support for centralized authentication using CAS (Central Authentication Service). CAS is a ticket-based authentication scheme that relies on a central authentication server.
9.3.1. How CAS works
The following figure outlines the authentication phase of the CAS authentication process:
The following figure shows the ticket validation process. Given, that the user already authenticated against CAS, the AuditConsole needs to validate the granted ticket by asking the CAS for validation.
Preparing the CAS Setup
In order for the AuditConsole to successfully connect to the CAS server, the CAS server's certificate used for HTTPS needs to be known to the AuditConsole, i.e. the Java environment that is running the AuditConsole.
Adjusting your cas.properties
WEB-INF/cas.properties and need to contain your CAS server URL
as well as the public address of your AuditConsole server.
The following example
cas.properties shows the settings for authenticating
the AuditConsole at http://console.jwall.org against the CAS server running
at https://auth.jwall.org:
# the CAS authentication server # cas.server.url=https://auth.jwall.org/cas # the AuditConsole service URL # console.server.url=http://console.jwall.org
No comments:
Post a Comment