Readme.txt 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. There are two subdirectories in this project;
  2. server - this is not a real maven sub-project in the sense that it builds anything. It is just here to allow you to
  3. conveniently run the CAS server using the maven Jetty plugin with our preconfigured SSL certificates.
  4. client - this contains the actual sample web application which uses the cas server for authentication. It uses the same
  5. certificates. In practice, the CAS server would likely be running on a different machine and both client and
  6. server would have different certificates issued to the server hostname.
  7. Running the CAS Server
  8. -----------------------
  9. You first need to download the CAS server 3.2.1 distribution from
  10. http://www.ja-sig.org/products/cas/downloads/index.html
  11. You only need the modules/cas-server-webapp-3.2.1.war web application file from the distribution. Copy this to the
  12. "server" directory inside the one that contains this readme file (i.e. copy it to samples/cas/server).
  13. You can then run the CAS server (from the same) by executing the maven command
  14. mvn jetty:run-war
  15. This will start the server on
  16. https://localhost:9443/cas
  17. If you point your browser at this URL, you should see the CAS login screen.
  18. Running the Client Application
  19. -------------------------------
  20. Leave the server running and start up a separate command window to run the sample application. Change to the directory
  21. samples/cas/client and execute the command
  22. mvn jetty:run
  23. This should start the sample application on
  24. http://localhost:8080/cas-sample/
  25. Try to access the secure page (as with the other samples) and you should be redirected to the CAS server to log in. Note
  26. that the sample authentication module that comes with the CAS server webapp will authenticate any user whose password
  27. matches the username. So you have to log in here as rod/rod, dianne/dianne etc. Obviously the usernames must still match
  28. those listed in the application's user-service.
  29. $Id$