We are in the process of evaluating EZproxy and are seriously considering replacing WAM, but have the opportunity to turn on the wam_sslhost_replace option in the mean time. I'm trying to determine if it is worth our time to move to the wam_sslhost_replace method, even though it might be short-lived. Can anyone who is using wam_sslhost_replace answer the following questions? Or if you've skipped it and just gone to EZproxy, I'd like to hear that too.
Which resources are not working with wam_slhost_replace? (I've seen mention on the forum of Facitva, Sage, Refworks and Alexander Street Press embed codes.)
Is it a fairly painless process, or is there work to do? I notice that you only have to change starting URLs that are https to begin with. Did you spend a lot of time changing bib record links?
When did you implement the option? Was it quick and easy enough to do during the semester, or did you wait for a break to switch?
Besides not having to constantly add entries to a SAN certificate and saving money with a more economical wildcard cert, are there any other benefits that you are seeing?
Are there any other problems you have run into?
Do you still wish you had EZproxy options that aren't in WAM?
Thanks in advance,
Library Systems & Digital Collections Administrator
ArtCenter College of Design