Signed certificates created for integrations need to be signed on your own owned domainIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; } .hd3{ color: #7a7a7a; font-weight:; font-size:16 px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14 px; text-decoration:; } body.c5 {height: 100%;} td.c4 {vertical-align: middle; text-align: left;} td.c3 {width: 50; vertical-align: middle; text-align: center;} img.c2 {align: baseline;} hr.c1 {border-top-width: 1px; border-top-style: solid; border-top-color: #cccccc;} --> Signed certificates created for integrations need to be signed on your own domain ProblemIntegrations like Ebonding, Oauth, Web services, and mutual authentication, sometimes require an asymmetric (private/public) certificates. When working with public certificates, these integrations may need them signed by a Certificate Authority (CA).CauseMost integrations would only require the SSL connection, for which the public SSL certificate on the instance is enough. However, when an integration needs a public and private key certificate, due to security policies, Servicenow does not provide new signed certificates to be used on integrations. ResolutionCustomers can work with the public signed certificates available on the instance to integrate using SSL. However, when a private/public certificate is required, customers need to generate these certificates with a common name (cn) on a domain owned by them. To generate a signed certificate for your integration, you should have the following information: Common Name: The fully-qualified domain name, or URL, that you own. Do not use "*.service-now.com."Organization: The legally-registered name for your business. If you are enrolling as an individual, enter the certificate requestor's name.Organization Unit: If applicable, enter the DBA (doing business as) name.City or Locality: Name of the city where your organization is registered/located. Do not abbreviate.State or Province: Name of the state or province where your organization is located. Do not abbreviate.Country: The two-letter International Organization for Standardization (ISO) format country code for where your organization is legally registered. After you have the information available, perform the following steps: Generate a Java Keystore or SSL certificate to be signed.The steps are provided by your Certificate Authority.Provide the required information to the Certificate Authority.Install the signed Java Keystore or SSL certificate on the instance. We recommend PEM format for public certificates, and a storetype jceks for a java keystore. Note: Request for signed certificate should not be on ".service-now.com." Use a domain your company owns.