[an error occurred while processing the directive]
![]() |
cosign-discuss at umich.edu |
general discussion of cosign development and deployment | |
--Jarod Malestein --University of Michigan --ITCS
Hi Jarod,
Can I get the InstallShield 7 project files? Could these be included in the IISCosign CVS project?
Cheers
Brett
------------
Brett Lomas Integration Architect Information Technology Systems and Services The University of Auckland New Zealand
Phone: +64 9 3737 599 extn 86499 Mobile: +64 21 757 096
-----Original Message----- From: jarod@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx [mailto:jarod@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of jarod@xxxxxxxxx Sent: Tuesday, 13 April 2004 9:56 a.m. To: Phil Pishioneri; Cosign Discussion Subject: Re: runtime requirements for IISCosign
Phil,
Almost everything you need to run IISCosign is included with the installer. The installer registers the MSXML 4.0 dlls for you. (If you'd like to make sure, check to see that msxml4.dll and msxmlr4.dll are in your \windows\system32 folder.)
The extra run-time requirements involves SSL certificates. You will need a certificate authority file as well as a private key and a signed certificate. The installer comes with the umweb.CA file which is pretty useless to anyone outside of U-M. If you'd like to customize the installer for your organization -- anybody -- we can get you the source code and project files for the installer. It uses Installshield 7. Also feel free to provide any suggestions to make the installer more institutionally agnostic. That is something we can certainly provide!
Were you having trouble getting IISCosign to load? Did any of this help?
--Jarod Malestein --University of Michigan --ITCS
--On Monday, April 12, 2004 5:36 PM -0400 Phil Pishioneri <pgp@xxxxxxx> wrote:
> Using the pre-built IISCosignInstaller 1.0.0 on Win2k3, IIS 6: > > I've found the extra registry key, and permissions that need to be set > for Win 2003, and did those. > > Also found references to libsnet, OpenSSL, and MSXML at cowboybebop. Do > I need to install MSXML and a separate OpenSSL (one appears to be > included in the installation) just for run-time support? (libsnet is > listed as only required if you want to compile IISCosign.) >