Introduction to each profile in Cas server

All the configuration files in Cas server are placed under the Web-inf directory and its subdirectories.

The configuration files under Web-inf/classes are:

L cas-theme-default.properties: The file is stored in the path of the CSS file, where the user can specify the CSS file to use as a custom CSS file, or you can change the default style of the corresponding CSS file in the configuration file.

L Series Messages_*.properties: International support for the corresponding resource files.

L default_views.properties and protocol_views.properties: A view configuration file used in Cas server that defines the processing class for the corresponding view and its file path.

L log4j.xml: log4j configuration file.

The configuration files under the Web-inf root directory are:

L Web. XML: This file is a familiar Web. xml file.

L cas-servlet.xml: This file is a spring MVC configuration file used by CAS server, which defines some controller and view related content.

L cas.properties: This file is the primary file for CAS server configuration. The external properties used by all spring-related configurations are defined in this file.

L deployerconfigcontext.xml: This file is a file that is specifically extracted for CAS server deployer, where the content is usually what the CAS server deployer needs to make changes to.

L login-webflow.xml: Log in to the spring Web flow profile used.

L restlet-servlet.xml: The associated configuration of the RESTful API to use.

L web-inf/spring-configuration: This directory contains the spring-related configuration files loaded by CAS server.

L web-inf/unused-spring-configuration: This directory is not used, but it is possible to copy them to the Spring-configuration directory if necessary.

The configuration files in the Web-inf/spring-configuration directory are all spring-related configuration files used in CAS server, specifically:

L applicationcontext.xml: This file defines the beans that are used primarily, and usually does not need to be modified.

L argumentextractorsconfiguration.xml: The protocol that needs to be used is defined in the file, and only CAs and SAML are available by default.

L log4jconfiguration.xml: log4j initialization of the corresponding configuration.

L propertyfileconfigure.xml: Specifies the location of the external property file, which is specified by default as the previously mentioned cas.properties file.

L securitycontext.xml: This is a configuration file for the spring security-related content used in CAs server and does not need to be modified by default.

L ticketexpirationpolicies.xml: Used to specify expiration policies for ticketgranting ticket and service ticket, generally no modification is required.

L ticketgrantingticketcookiegenerator.xml: ticketgranting ticket corresponds to the configuration of the Cookiegenerator.

L ticketregistry.xml: defaultticketregistry corresponds to the configuration.

L uniqueidgenerators.xml: Unique primary key generation related configuration.

L warncookiegenerator.xml: The cookiegenerator corresponding configuration used to generate the warning.

(Note: This article was written based on CAS 3.5.2)

(Note: Original article, reproduced please indicate the source.) Original address: http://haohaoxuexi.iteye.com/blog/2128865)

Introduction to each profile in Cas server