[Geoserver-devel] [jira] (GEOS-5321) Finalize migrating CAS to an extension

Christian Mueller created ImprovementGEOS-5321
Finalize migrating CAS to an extension

Issue Type:

ImprovementImprovement

Affects Versions:

2.3-beta1, 2.2.1

Assignee:

Andrea Aime

Components:

Security

Created:

22/Sep/12 9:16 AM

Description:

Hi Justin, I applied my cumulative patch for the CAS module. Two things to do

  1. You can include the cas module in the build, it should be listed as an extension in 2.2.1 and 2.3.x, e.g http://geoserver.org/display/GEOS/Latest

  2. There are some CAS validation messages in GeoserverException.properties of the main module. I think the CAS module should have its own GeoserverException.properties file. The messages I am talking about are

CasFilterConfigException.CAS_SERVICE_URL_REQUIRED=Service URL required
CasFilterConfigException.CAS_SERVER_URL_REQUIRED=CAS server URL required
CasFilterConfigException.CAS_SERVICE_URL_MALFORMED=Service URL syntax error
CasFilterConfigException.CAS_SERVER_URL_MALFORMED=CAS server URL syntax error
CasFilterConfigException.CAS_URL_IN_LOGOUT_PAGE_MALFORMED=“Syntax error in URL for CAS logout page”
CasFilterConfigException.CAS_PROXYCALLBACK_MALFORMED=Syntax error in proxy callback URL
CasFilterConfigException.CAS_PROXYCALLBACK_NOT_HTTPS=Proxy callback URL must use HTTPS
CasFilterConfigException.CAS_PROXYCALLBACK_HOST_UNEQUAL_SERVICE_HOST=Proxy callback host differs from service host

Project:

GeoServer

Priority:

MajorMajor

Reporter:

Christian Mueller

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your [JIRA administrators](https://jira.codehaus.org/secure/ContactAdministrators!default.jspa). For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)