Coldfusion: Difference between revisions
From RavenWiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* Download the [http://raven.cam.ac.uk/project/java-toolkit/ Raven Java Toolkit] and extract webauth-toolkit.jar to runtime\jre\lib\ext in the Coldfusion installation directory. | * Download the [http://raven.cam.ac.uk/project/java-toolkit/ Raven Java Toolkit] and extract webauth-toolkit.jar to runtime\jre\lib\ext in the Coldfusion installation directory. | ||
* Restart the Coldfusion service. | * Restart the Coldfusion service. | ||
* Download [http://www.emma.cam.ac.uk/files/ravencfc.zip ravencfc.zip] and extract to the directory you wish to protect. It should contain | * Download [http://www.emma.cam.ac.uk/files/ravencfc.zip ravencfc.zip] and extract to the directory you wish to protect. It should contain 4 files: application.cfc, webauth.cfc, index.cfm and pubkey2.crt. | ||
* All Coldfusion files at or below the directory should now be protected. If you wish to protect binaries etc. then combined use of the Apache/IIS module to protect those directories is suggested. | * All Coldfusion files at or below the directory should now be protected. If you wish to protect binaries etc. then combined use of the Apache/IIS module to protect those directories is suggested. | ||
The steps above have only been tested with Coldfusion MX 7.02. It is good practice to move the webauth.cfc file to a non-public filepath on production servers. | The steps above have only been tested with Coldfusion MX 7.02. It is good practice to move the webauth.cfc file to a non-public filepath on production servers. | ||
Revision as of 15:24, 30 January 2007
Tom Corder (tac21) has written a Coldfusion wrapper for the Raven Java Toolkit.
Installation Steps:
- Download the Raven Java Toolkit and extract webauth-toolkit.jar to runtime\jre\lib\ext in the Coldfusion installation directory.
- Restart the Coldfusion service.
- Download ravencfc.zip and extract to the directory you wish to protect. It should contain 4 files: application.cfc, webauth.cfc, index.cfm and pubkey2.crt.
- All Coldfusion files at or below the directory should now be protected. If you wish to protect binaries etc. then combined use of the Apache/IIS module to protect those directories is suggested.
The steps above have only been tested with Coldfusion MX 7.02. It is good practice to move the webauth.cfc file to a non-public filepath on production servers.
