This is a list of frequently asked questions (FAQ) for the InCommon Certificate Service.
- General Questions
- What is the InCommon Certificate Service?
- What does the service cost?
- Are personal certs and code-signing certs included in the cost?
- Who can subscribe to the InCommon Certificate Service?
- Can we take advantage of the certificate service without participating in federated identity services?
- Is Shibboleth a technical requirement for using the Certificate Service?
- Why is this program attractive to my institution?
- What is Comodo's role in this service?
- Are there any types of certificates excluded from this program?
- How do I sign up for this program?
- What if my campus operates domains other than their primary institutional .edu domain?
- What is the required term of participation?
- Why are Internet2 members being given a 25 percent discount for participation?
- Why is InCommon membership required for participation?
- How does an institution actually acquire certificates?
- What types of interfaces will an institution have to Comodo for certificate issuance and general program administration?
- What is the Certificate Services Manager (CSM)?
- How many certificate profiles are supported and what do they cover?
- Can I have my own Campus Root issued under the InCommon hierarchy?
- Will the certificates issued via this program be recognized by other federations?
- Are non-profit regional research and education networks and other organizations within the .edu domain eligible?
- What is the certificate chain for SSL certificates issued by the InCommon Certificate Service?
- Where can I obtain a seal?
- Will certificates issued by the Certificate Service comply with the emerging InCommon Identity Assurance Profiles (Bronze/Silver)?
- What is the certificate chain for Extended Validation (EV) SSL/TLS certificates issued by the InCommon Certificate Service?
- Do I need to install any certificates in my browser to access web sites that use SSL or EV certificates issued by the InCommon Certificate Service?
- What is the best way to test a server configured with an SSL or EV certificate issued by the InCommon Certificate Service?
The InCommon Certificate Service, created by and for the higher education community, provides unlimited server and personal certificates for one low membership fee. This includes unlimited SSL certificates, Extended Validation (EV) SSL certificates, client (or personal) certificates, and code signing certificates.
Please see the official fee schedule. Internet2 members receive a 25 percent discount.
Yes, both are included in the base price.
Any higher education institution with its primary location in the United States, who qualifies for a domain in the .edu name space, may subscribe, as well as not-for-profit regional research and education networking organizations in the United States. Subscribers must be InCommon participants or must join InCommon to be eligible for the Certificate Service.
Can we take advantage of the certificate service without participating in federated identity services?
Yes. You must join InCommon but you don't need to use the federated identity services.
No, but we are investigating using federated identity management to simplify access to the Certificate Services Manager.
The higher education community developed this service to reduce the cost of certificates. Because InCommon is a non-profit, community-driven organization, the primary drivers are to provide value and benefits to the subscribers (rather than providing profit for the certificate provider). The program offers unlimited certificates at one annual fee, which is expected to reduce the cost of certificates for many institutions.
Comodo is the certificate authority and InCommon has contracted with Comodo for the deep discounts made available to colleges and universities. As a commercial certification authority, Comodo has extensive knowledge of the marketplace and attractive features. Comodo has been operating a similar service with TERENA, the Trans-European Research and Education Networking Association. TERENA's positive association with Comodo, and its significant software development for the Comodo APIs, made this partnership attractive to InCommon and Internet2.
This program includes all certificates listed above. The program allows institutions to issue so-called wild-card certificates. A primary advantage of wild-card certificates has been to allow a reduction of the number of certificates purchased. Given that in this program there is no longer a price penalty for issuance of additional SSL certs, institutions may want to reconsider the use of wild-card certificates, as some security experts believe that such certificates reduce security due to the extra burden of managing private keys in multiple locations.
There is a Certificate Service Subscriber Agreement stored in our document repository. The Subscriber Agreement is an addendum to the InCommon Participation Agreement. InCommon participation is required to take advantage of the certificate service.
Any domains administered by the institution (e.g., a professional society with a .org domain or even a .com domain) can qualify, as long as the institution can prove that it is the administrative manager for that domain. The key requirement is that the institution be the administrator of record for these domains and organizations.
Initially, institutions are required to commit to participation for an initial term of three (3) years, with the cert service fee billed annually.
InCommon is wholly owned by Internet2, and Internet2 is providing the initial capital required to launch the program.
This program is an extension of the trust services already being provided and managed by InCommon, and will require InCommon resources, including staff time and effort. In particular, implementation of this program will take advantage of the Registration Authority (RA) already managed by InCommon for establishing the trust services structure with participants.
InCommon operates the Registration Authority, leveraging its current processes for verifying organizations and identity proofing officials authorized to act on behalf of an institution for certificate issuance. These individuals may be the same or different than the current InCommon administrators. It is expected that at each institution a small number of people (typically two or three) will be authorized to manage the overall institutional certificate program.
Once an institution authorizes individuals, they will deal directly with the Comodo CA (via either a GUI or the API) for requesting individual certificates. InCommon is, by design, not in the path of certificate issuance or revocation (or even in the path of authorizing second-level personnel), only the vetting of the top-level certificate program administrators and the domains they are authorized to administer.
What types of interfaces will an institution have to Comodo for certificate issuance and general program administration?
Comodo offers both a GUI (called the Comodo Certificate Services Manager, CSM) and an API to their service for certificate issuance, management of second-level personnel and institutional policies for certificate structure, as well as support in matters such as certificate revocation.
The CSM is the web-based interface used to request and manage your certificates.
There are seven (7) profiles available to participants:
- SSL Server certificate (standard SSL/TLS cert—includes certs with SANs)
- SSL Wildcard certificate (SSL/TLS cert with a wildcard CN)
- Extended Validation (EV) Server Certificate—issued directly by Comodo and subject to Comodo's domain vetting processes, terms and conditions and CPS, but at no extra charge beyond the base InCommon certificate service fee.
- Code Signing certificate (for signing software that can be trusted when distributed with, for example, jar files, etc.)
- User certificate (Digital Signature) (for signing email, documents, or authenticating to PKI based services)
- User certificate (Encryption) (for encrypting email, documents, or symmetric keys used to secure data). Comodo has made available a centralized key escrow service, but this is not part of the basic set of services offered in this program at this time. It is available as an add-on.
- User certificate (Dual Use) (a combination of the above two)—Comodo has made available a centralized key escrow service, but this is not part of the basic set of services offered in this program at this time. It is available as an add-on. Escrow of dual use certificates is potentially problematic however because it may eliminate the non-repudiation characteristic of signing certificates.
The initial release of this program does not provide this functionality, but this option is available under the agreement with Comodo. When the GUI for certificate life cycle management has the capability of supporting this option, it is anticipated that institution-based subordinate CAs (and campus-specific profiles and practice statements) will be made available to members who desire this functionality for an additional cost.
This functionality is anticipated for a later release of the program based on the demand from the InCommon community. The agreement with Comodo allows for cross-signing of other CAs at an additional cost.
Are non-profit regional research and education networks and other organizations within the .edu domain eligible?
Not for profit regional research and education networking organizations with primary offices in the United States that are not housed within an otherwise eligible educational institution may join this program by paying an annual fee of $2,000. No further discounts are applicable to this fee. In all cases, participation in this program is solely to allow the organization to acquire certificates for staff within that organization and for servers and services operated directly by the organization. Participation explicitly excludes the ability for the organization to issue certificates to members of the organization or to resell the service to members of the organization. This fee also applies to any non-Carnegie classified organizations who qualify for participation (i.e., organizations in the United States who currently have a .edu domain). All participating organizations must still join InCommon as is required for all participants in this program.
See the InCommon Certificate Types for answers to this and similar questions.
Please visit http://www.trustlogo.com/install
Will certificates issued by the Certificate Service comply with the emerging InCommon Identity Assurance Profiles (Bronze/Silver)?
The InCommon PKI subcommittee will ensure that the certificates align with the Identity Assurance Profiles.
What is the certificate chain for Extended Validation (EV) SSL/TLS certificates issued by the InCommon Certificate Service?
See the InCommon Certificate Types for answers to this and similar questions.
Do I need to install any certificates in my browser to access web sites that use SSL or EV certificates issued by the InCommon Certificate Service?
No, you do not need to install any certificates in the browser. The AddTrust root CA certificate, which is required for browser access, ships with all known browsers. In general, intermediate CA certificates are passed from the server to the browser as needed, so yes, there is a certificate bundle that needs to be installed on the server, but not in the browser.
If you are a site administrator testing a new server configuration, there is one caveat, however. Some browsers (such as Firefox) will store intermediate CA certificates received from a server in the browser's certificate store, so unless you're careful, you may be tricked into believing your server is configured correctly when in fact it's not. Be sure to remove intermediate CA certificates from your browser's certificate store before testing your server configuration.
What is the best way to test a server configured with an SSL or EV certificate issued by the InCommon Certificate Service?
Be wary of using a browser to test your server configuration. Some browsers (such as Firefox) will store intermediate CA certificates received from a server in the browser's certificate store, so unless you're careful, you may be tricked into believing your server is configured correctly when in fact it's not. To avoid this pitfall, use openssl to definitively test your server configuration:
$ openssl s_client -connect server:port -CApath /etc/ssl/certs/
If the client machine does not have the /etc/ssl/certs/ directory, try the following command instead:
$ openssl s_client -connect server:port -CAfile comodoroot.crt
In either case, if certificate validation passes, you know your server is configured correctly. Note that /etc/ssl/certs/ and comodoroot.crt contain root certificates only; no intermediate CA certificates are included.