Mock Eureka! Clinical Central Authentication Service
Georgia Clinical and Translational Science Alliance (Georgia CTSA), Emory University, Atlanta, GA
What does it do?
It provides a mock CAS server for system tests of Eureka! Clinical components. It responds to the following CAS protocol version 2 URLs:
/login
(it auto authenticates the user as thesuperuser
)/logout
/serviceValidate
/proxy
/proxyValidate
The responses are hard-coded.
Version 2.1
Support proxy callbacks, which are needed for proxy support to work.
Version 2.0
No feature changes. This release only updates dependencies.
Version 1.0
Initial release. Supports all features of CAS that Eureka! Clinical uses.
Build requirements
Runtime requirements
Building it
The project uses the maven build tool. Typically, you build it by invoking mvn clean install
at the command line. For simple file changes, not additions or deletions, you can usually use mvn install
. See https://github.com/eurekaclinical/dev-wiki/wiki/Building-Eureka!-Clinical-projects for more details.
Installation
This project is intended for other Eureka! Clinical web applications to depend on it for running in embedded Tomcat. All that is needed is for the tomcat maven plugin to add it as a dependency, and for Eureka! Clinical web applications to use https://localhost:8443/cas-mock
as the CAS server URL.
For standalone deployment, do the following:
- Stop Tomcat.
- Remove any old copies of the unpacked war from Tomcat's webapps directory.
- Copy the warfile into the Tomcat webapps directory, renaming it to remove the version. For example, rename
cas-mock-1.0.war
tocas-mock.war
. - Start Tomcat.
Maven dependency
<dependency>
<groupId>org.eurekaclinical</groupId>
<artifactId>cas-mock</artifactId>
<version>version</version>
</dependency>
Developer documentation
Getting help
Feel free to contact us at [email protected].