Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Paris Now Platform Capabilities Now Platform capabilities Connections and Credentials Getting started with credentials External credential storage CyberArk credential storage integration CyberArk integration configuration Configure the MID Server for CyberArk

    Configure the MID Server for CyberArk

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Configure the MID Server for CyberArk

    Configure the config.xml file to grant the MID Server access to the CyberArk vault.

    Before you begin

    Role required: admin

    Before starting this procedure, import the JavaPasswordSDK.jar file into the instance.

    Procedure

    Manually configure the MID Server config.xml file with these parameters.

    This configuration cannot be done from the instance.

    Table 1. Required configuration parameters
    Parameter Value Description
    ext.cred.safe_folder NameOfFolder Folder to use for all credential lookups. For example, root.
    ext.cred.use_cyberark true Boolean parameter indicating that this MID Server is integrated with CyberArk.
    Table 2. Optional configuration parameters
    Parameter Value Description
    ext.cred.safe_timeout 5 (sec) Timeout of each credential lookup in the vault, specified in seconds.
    ext.cred.safe_name NameOfSafe Default safe name used for all credential lookups. If parameters are in multiple safes, the credential ID may be specified in the format <safeName>:<CredentialID>. When configured like this, the NameOfSafe field is ignored. If all external credentials have their credential IDs specified in this format, then leave out the NameOfSafe field.
    Note: By default the separator character in this format is a colon. To assign any character you want as a separator, add this line to the CredMap.properties file: safe.cred.split.string=<string>.
    ext.cred.app_id ServiceNow_MID_Server Specifies the App-ID used to grant permission to the MID Server to access the CyberArk vault. The default value, ServiceNow_MID_Server, must be defined in the CyberArk vault. You can use this parameter to override the default and specify your own App-ID. If you edit the App-ID in this parameter, make sure to configure CyberArk to match.
    ext.cred.type_specifier true Forces an IP address lookup to return credentials that match both the CyberArk platform ID and the IP address. For example, if an IP address is shared by both Windows and Tomcat, a credential with a platform ID starting with Win returns the Windows credential only. When this parameter is set to true, CyberArk looks for platform IDs that begin with:
    • Win: Windows
    • Unix: SSH
    • VMWare: VMware
    ext.cred.check_ssh_type false When set to true, requires that the type of SSH credential returned from CyberArk matches the type of credential requested. For example, if a normal SSH username/password credential is requested and only SSH keys are available, the credential lookup fails.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Configure the MID Server for CyberArk

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Configure the MID Server for CyberArk

      Configure the config.xml file to grant the MID Server access to the CyberArk vault.

      Before you begin

      Role required: admin

      Before starting this procedure, import the JavaPasswordSDK.jar file into the instance.

      Procedure

      Manually configure the MID Server config.xml file with these parameters.

      This configuration cannot be done from the instance.

      Table 1. Required configuration parameters
      Parameter Value Description
      ext.cred.safe_folder NameOfFolder Folder to use for all credential lookups. For example, root.
      ext.cred.use_cyberark true Boolean parameter indicating that this MID Server is integrated with CyberArk.
      Table 2. Optional configuration parameters
      Parameter Value Description
      ext.cred.safe_timeout 5 (sec) Timeout of each credential lookup in the vault, specified in seconds.
      ext.cred.safe_name NameOfSafe Default safe name used for all credential lookups. If parameters are in multiple safes, the credential ID may be specified in the format <safeName>:<CredentialID>. When configured like this, the NameOfSafe field is ignored. If all external credentials have their credential IDs specified in this format, then leave out the NameOfSafe field.
      Note: By default the separator character in this format is a colon. To assign any character you want as a separator, add this line to the CredMap.properties file: safe.cred.split.string=<string>.
      ext.cred.app_id ServiceNow_MID_Server Specifies the App-ID used to grant permission to the MID Server to access the CyberArk vault. The default value, ServiceNow_MID_Server, must be defined in the CyberArk vault. You can use this parameter to override the default and specify your own App-ID. If you edit the App-ID in this parameter, make sure to configure CyberArk to match.
      ext.cred.type_specifier true Forces an IP address lookup to return credentials that match both the CyberArk platform ID and the IP address. For example, if an IP address is shared by both Windows and Tomcat, a credential with a platform ID starting with Win returns the Windows credential only. When this parameter is set to true, CyberArk looks for platform IDs that begin with:
      • Win: Windows
      • Unix: SSH
      • VMWare: VMware
      ext.cred.check_ssh_type false When set to true, requires that the type of SSH credential returned from CyberArk matches the type of credential requested. For example, if a normal SSH username/password credential is requested and only SSH keys are available, the credential lookup fails.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login