Set up the Google Cloud Translator Service spoke

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 5 minutes de lecture

    • Integrate your Google account with your ServiceNow instance.

    Avant de commencer

    • Request an Integration Hub subscription.
    • Activate the Google Cloud Translator Service spoke.
    • Create a service account on Google Cloud, generate a service account key of JSON type and download it. For information on creating the service account key, see the Google documentation.
    • Enable the Cloud Translation API service. For information on enabling a service, see the Google documentation.
    • Role required: admin

    Create a Java KeyStore certificate

    Encrypt the security certificates obtained from Google by creating a Java KeyStore (JKS) file.

    Avant de commencer

    • Role required: admin
    • Download a JSON file containing the service account key from Google. For information on downloading the JSON file, see the Google documentation. Following is a sample JSON file:
      {
  "type": "service_account",
  "project_id": "primeval-nectar-242610",
  "private_key_id": "0c6c7b1511f1c236c1300c5933d528bbf45314e5",
  "private_key": "-----BEGIN PRIVATE KEY-----\nMIIEvQKBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDg97zOxfOenyu2\niXC8ArQHaAgOiy27sjG3jJXohUdHkawuX+nQLWZkIbZYlZX+cMjNfpUFpzeHRkPm\n5OQ2bjHCgCTVFCbToKIH+VkMpS7LO+TFKW2TkWJHzWO2Xv30bT+2HkSb4tTZisMg\nV/sI6dGJaOko4yTIBwZc7vlr28nGJdw945+9NVkEPm/G8drYJRTlrImyfnnD0RGR\npyKctHAC3wZ/rCE5b/VIHK5ZKspRT/qXVwZsH5pW7a8NDrB1z+YQIGGOjlfINxBE\nQCE5GhiUF+XscfGdq30culFoILO9xAk/41yQb8ziDr4Ru5H1UF0ljp4t6fLw3k2o\noDsr+R+XAgMBAAECggEAA03QIY9JsSowR6mEE+YsQ7GU8LW9kbSfw0zWxMf0UIpE\np5e0BOEt0EmodmuX/NkmMdJqmN8oUx3GkIULDvuWUn90SwbVPSVuS8SvOJ7SbZyv\nEvA1UkX/1gMftEV34FecaG3QXyO5MYq2q+pu3uYkNCrsxbN0TlXAE6xU0G81auoL\nYIl7pzVfcxDW5Of5VI5AuMc8+0rgadvOPu3JThjjauMvnDPKi5sbKDsDCfTqqDys\nHMny8+uhfCOr2JtTgpc4HUgqGKpALAUQvRZYmmlKqfBNgXo+dDBKJsd7pD9NnxQn\nM7l8wqQ0kS2kfcJsHNcV4ZUORabz1q1MFlVdxxeijQKBgQD5r7J/MgN4LLekaimE\n3T27KTA12aikQl0LORQHLbHZRexVD41WoRrQySSzUvQKXSiwZwRQLO/hptDRnUyh\n6WVQLwtSiNvItLu+8Ak2mb3F+NDEFb/R1FPdTR30G7wXEeau1+cm8+8N63ehFAW4\n7IXTyDhtO5c3deXN7SDrRFjrnQKBgQDmqAdRkKPwau6q+zSGPxqcFqlXS+ghpQkT\nUPxe45aZdRuFUOUCWA9BIbMnlVHZUDnQpiIbfBJ9Tcs2/vBwLt2QjziZPbnIlmkp\nqIF4t5edar8Z6vn0lWmeupAmlFqKN7GoopUD+RIto68BfSKIPczfGLtu3PxLEmgj\nRYzY5HUTwwKBgCZ05zssCtjBmm9aYpayNMXU7DX/FjhmeEo4Olt4sEHUwTfAs3Y6\nThUGRf7QsgG+o3u4AjQPF8tblCIU5i6x8gbNmCLYLXHWVGxuMB0WxOHvFsh8yRSa\nbWhSbmCgvPGYsj0Px+x5+cHdGInYuaDn3RznY7l/SiUipYh4E2/pEQEJAoGAdu1G\nMMESNkD8ZD5324wn7TkmATPLMaXFYydLqKVSHjeqg/eszKOY4e09UXiFJjZeSP2P\n8nnrkp4M3INgd4dCiGnANgsEgq9C887FSvfmfazvca6dSIXNWqE4+Btf/4ot2RRT\nHyRKQiv2bR8XMgYjXxiCc+wPTank9eLDd4V79D8CgYEA6Eywngil5bVO5ksW9gyp\n0u5eieKMNYndPq5lyw1POyN9nx/iYQ3m2FI7d2K7aBpK0AXkLZQqv5tbqrF2fvdO\nbm4eLISLg8kdZ09OohAsRuZ6JG2aICw4vTWgQyRWLe4RxdoY9gGKh8N844tUU7uN\nPCsWu/rdB8dT8wqerTFo81U=\n-----END PRIVATE KEY-----\n",
  "client_email": "service-now-google-trans-v3@primeval-nectar-242610.iam.gserviceaccount.com",
  "client_id": "113255944370425109391",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/service-now-google-trans-v3%40primeval-nectar-242610.iam.gserviceaccount.com"
}

    Procédure

    1. In the JSON file, perform the following for the private_key value.
      1. Unescape the \n characters.
        Conseil :
        To unescape characters in a JSON file, you can parse a JSON string into a JavaScript object.
      2. Store the private key in a file with .pem extension.
    2. In the JSON file, perform the following for the client_x509_cert_url value.
      1. Open the link specified for client_x509_cert_url.
      2. Unescape the \n characters for the certificate associated with the private_key_id mentioned in the JSON file.
      3. Store the certificate value in a file with .pem extension.
    3. Use the openssl command to create a PKCS 12 file using the recently created private key and certificate files. 
      openssl pkcs12 -export -in [path to certificate] -inkey [path to private key] -certfile [path to certificate ] -out testkeystore.p12

      For example, if certificate.pem is the certficate and privatekey.pem is the private key:

      openssl pkcs12 -export -in certificate.pem -inkey privatekey.pem -certfile certificate.pem -out testkeystore.p12
      A PKCS 12 file, testkeystore.p12, is created.
    4. Specify an export password or source keystore password.
      Remarque :
      You should specify this password when creating a JWT key for Google Cloud Translator Service spoke.
    5. Use the keytool command to create a JKS file from the PKCS 12 file. 
      keytool -importkeystore -srckeystore testkeystore.p12 -srcstoretype pkcs12 -destkeystore wso2carbon.jks -deststoretype JKS
      Remarque :
      testKeyStore.p12 is the PKCS 12 file and wso2carbon.jks is the JKS file.
    6. Specify a destination keystore password.
      Remarque :
      You should specify this password when attaching a JKS certificate to Google Cloud Translator Service spoke.

    Attach a Java KeyStore certificate to Google Cloud Translator Service spoke

    Enable the JWT client authentication by attaching a valid Java KeyStore (JKS) certificate to Google Cloud Translator Service spoke.

    Avant de commencer

    • Role required: admin
    • Valid Java KeyStore certificate

    Procédure

    1. Navigate to All > System Definition > Certificates.
    2. Click New.
    3. On the form, fill in the fields.
      Tableau 1. X.509 Certificate form fields
      Field Description
      Name Identifier of the certificate.
      Notify on expiration Users to be notified when the certificate expires.
      Warn in days to expire Number of days to send a notification before the certificate expires.
      Active Option to activate the certificate.
      Type Type of the certificate. Select Java Key Store.
      Expires in days Number of days until the certificate expires.
      Key store password Password to access the certificate. Use the destination keystore password specified when creating the JKS certificate. For more information on this password, see Create a Java KeyStore certificate.
      Short description Summary about the certificate.
    4. Click the manage attachments icon (Attachments icon) and attach a JKS certificate.
    5. To validate the JKS certificate, click Validate Stores/Certificates.
    6. Click Submit.

    Create a JWT signing key for Google Cloud Translator Service spoke

    Assign a JSON Web Token (JWT) signing key to your Java KeyStore certificate.

    Avant de commencer

    Role required: admin

    Procédure

    1. Navigate to All > System OAuth > JWT Keys.
    2. Click New.
    3. On the form, fill in the fields.
      Tableau 2. JWT Keys form fields
      Field Description
      Name Identifier of the JWT signing key.
      Signing Keystore Valid JKS certificate for which you want to assign the key.
      Key Id Key ID to identify which key is used when multiple keys are used to sign tokens.
      Signing Algorithm Algorithm to sign with the key.
      Signing Key Password Password associated with the key. Use the export password or the source keystore password specified when creating the JKS certificate. For more information on this password, see Create a Java KeyStore certificate.
      Active Option to activate the key.
    4. Click Submit.

    Create a JWT provider for Google Cloud Translator Service spoke

    Add a JSON Web Token (JWT) provider to Google Cloud Translator Service spoke.

    Avant de commencer

    Role required: admin

    Procédure

    1. Navigate to All > System OAuth > JWT Providers.
    2. Click New.
    3. On the form, fill in the fields.
      Tableau 3. JWT Provider form fields
      Field Description
      Name Identifier of the JWT provider.
      Expiry Interval (sec) Number of seconds that indicate the lifespan of the JWT provider token. Specify 3600.
      Signing Configuration JWT signing key.
    4. Right-click the form header, and click Save.
    5. In the Standard Claims related list, enter the values for these claims.
      Tableau 4. Claim
      Claim name Claim value
      aud https://www.googleapis.com/oauth2/v4/token
      iss client_email value from the JSON file.
    6. In the Custom Claims related list, create the scope claim and enter its value as https://www.googleapis.com/auth/cloud-translation.
    7. Click Update.

    Configure the credential for the GoogleTranslation alias

    Authorize actions of Google Cloud Translator Service spoke by configuring the Google OAuth 2.0 credential.

    Avant de commencer

    Role required: admin

    Procédure

    1. Navigate to All > Connections & Credentials > Credentials.
    2. Select the Google OAuth 2.0 credential.
    3. Open the record specified in the OAuth Entity Profile field.
    4. In the JWT Provider field, specify the JWT provider that you want to use.
    5. Click Update.
    6. To verify if an OAuth Access token is generated to connect to Google's translation services, click the Get OAuth Token related link of the Google OAuth 2.0 credential.

    Configure the connection attributes for the GoogleTranslation alias

    Connect to the Google's translation service by configuring the Google connection. Provide information that is used by HTTP(s) actions or activities to connect to that service.

    Avant de commencer

    Role required: connection_admin

    Procédure

    1. Navigate to All > Connections & Credentials > Connections.
    2. Open for the record for Google.
    3. In the Attributes related list of the HTTP(S) Connection form, fill in the fields.
      Tableau 5. HTTP(S) Connection form fields
      Field Value required
      location Location of the customer. If the value is not specified when creating an account on Google Cloud, then specify global.
      project_id Identifier of a project. Specify the project_id value from the JSON file.
      version API version that the related spokes are built for. The default value is v3beta1.

      Because Google now supports the v3 version, you can override this value as v3.
    4. Right-click the form header and click Save.