Hi, This is the vendor requirement for wildcard . This is their defenition of wildcard In the following, Regular refers to a certificate that is issued in the exact name of your EZproxy server (e.g., ezproxy.yourlib.org) whereas Wildcard refers to a certificate that is issued as *. followed by the exact name of your EZproxy server (e.g., *.ezproxy.yourlib.org). These form of certificate names are the two types that can be created from within the SSL configuration option provided by EZproxy. ( we choose the above ) If you create a wildcard certificate outside of EZproxy that is a wildcard for your domain (e.g., *.yourlib.org) and if you are using proxy by hostname, you must edit config.txt and add "Option IgnoreWildcardCertificate" to indicate that your wildcard is not in the form EZproxy expects. If you do this, your wildcard certificate will behave as a Regular certificate, which includes providing browser warnings when https web sites are proxied. Note on wildcard certificates: EZproxy expects the wildcard domain name to be specified with the CN element in the Subject field. The non-wildcard domain should be specified as a DNS element in the Subject Alternative Name (SAN) field. yyyy.com.proxy.mycompany.com here yyyy.com a site which reside outside and proxy.mycompany.com is proxy server fqdn Thanks
... View more
