https://step.dev/knowledgebase/30/setup/configuration/ Recent content in Configuration on Step Documentation Hugo -- gohugo.io en Mon, 29 Jul 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/identity-management/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/identity-management/ Ldap setup (optional) You can use LDAP to authenticate to Step by uncommenting the following properties is step.properties: # Authenticator configuration - example for LDAP ui.authenticator=step.core.access.LdapAuthenticator # url of your LDAP server ui.authenticator.ldap.url=<url> # root named context for searching for users ui.authenticator.ldap.base=dc=<>,dc=<> # search filter - {user} will be replaced with the username ui.authenticator.ldap.filter=(cn={user}) # user used for connecting to the LDAP server ui.authenticator.ldap.techuser=cn=<>,dc=<>,dc=<> ui.authenticator.ldap.techpwd=<PWD> # Use following flag to manage users from LDAP (authenticated user will be created automatically in Step) #ui. https://step.dev/knowledgebase/30/setup/configuration/important-settings/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/important-settings/ Controller settings Main properties The main configuration file of the Controller is step.properties. Installation from archive When installing Step manually from the archives, the file is located in the conf folder of the controller. The main parameters to be updated in order to start the Controller are listed below : port=<port_to_access_controller_gui> grid.port=<port_for_agents_to_access_the_controller> datasource.mongo.properties.host=<mongo_hostname_or_ip> datasource.mongo.properties.port=<mongo_port> datasource.mongo.properties.username=<step_database_username> (if any) datasource.mongo.properties.password=<step_database_password> (if any) For example : port=8080 -> Controller GUI will be accessible on port 8080 grid. https://step.dev/knowledgebase/30/setup/configuration/licensing/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/licensing/ License (Enterprise version only) For the Step Controller Enterprise version, you will need to put your purchased Step license files in one of the following folders: [installation_path]/licenses/ (recommended) [installation_path]/bin/licenses/ Detailed explanation: The license files consist of a license configuration file (step-enterprise.licenseconfig.json), as well as (usually) one or more actual license files (license*.json). Please contact us to obtain the relevant files for your organization. Do not attempt to modify the content of these files, as they are digitally signed, and any change will render the signature invalid. https://step.dev/knowledgebase/30/setup/configuration/logging/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/logging/ This page describes how to configure the logging in the different component of Step. To customize the logback configuration using our Helm chart, refer to this documentation Controller logs By default, the controller logs are written to the file log/controller.log. The default logging settings can be changed in the file bin/logback.xml. Verbosity You can easily change the logging verbosity by tweaking the “root” log level present in the file bin/logback.xml. You can also tweak the verbosity for specific features. https://step.dev/knowledgebase/30/setup/configuration/ssl-settings/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/ssl-settings/ By default, the controller GUI is accessible via HTTP and SSL is disabled. It is highly recommended to secure your controller instance by enabling SSL. Before enabling SSL you will need a valid SSL certificate for your controller domain. You can either use a self-signed certificate or obtain it from a certificate authority (CA). In both cases you’ll get following files: the private key file (.key) the certificate file (.cert) The controller requires the certificate in a Java KeyStore in JKS format. https://step.dev/knowledgebase/30/setup/configuration/agent-sizing/ Tue, 08 Jul 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/agent-sizing/ Agents are responsible for executing automation (automated test, load test, etc) through Keywords. Their resource requirements can vary significantly depending on the type of automation, the automation tools used, and the nature of the application under test. This guide provides practical recommendations to help you size agents effectively for reliable, stable, and performant execution. For the general platform requirements and sizing recommendations, refer to the Requirements page. Why Agent Sizing Matters Properly sizing your agents is critical for ensuring predictable and efficient automation execution. https://step.dev/knowledgebase/30/setup/configuration/timeseries-settings/ Wed, 25 Sep 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/timeseries-settings/ How Time Series Works Step has its own implementation of time series, designed to efficiently manage and visualize large datasets over extended periods. This feature powers data visualization in the Performance tab of the execution view and the Analytics view. By grouping data into collections with different resolutions, the system optimizes both storage and retrieval for short-term and long-term analysis, ensuring high performance and resource efficiency. By default, Step uses several collections with varying resolutions to store data: https://step.dev/knowledgebase/30/setup/configuration/agent-configuration/ Wed, 01 May 2024 14:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/agent-configuration/ Agent endpoint The agent exposes a REST service to the Controller, which is consumed by the controller to execute Keywords. The endpoint of this service is called agent endpoint. The agent endpoint is configured automatically at agent startup and is communicated to the controller at registration. If required, the endpoint can be tweaked as follow: Agent port Per default the agent lets the system find a free port automatically at startup to listen on. https://step.dev/knowledgebase/30/setup/configuration/agent-provisioning-configuration/ Wed, 01 May 2024 14:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/agent-provisioning-configuration/ When running in Kubernetes, Step supports automatic provisioning of Agents (i.e. automatic provisioning of the containers responsible for executing Keywords). This page describes how to enable and configure the Agent provisioning. For information on using Agent provisioning, please refer to the Agent Provisioning page. Notes: Agent provisioning is part of Step Enterprise and is supported as of version 25. It has been designed to work with the official Step Helm Chart. https://step.dev/knowledgebase/30/setup/configuration/customization/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/setup/configuration/customization/ Cosmetics Cosmetics customization is only available as part of step enterprise Customization of step’s static resources (images, stylesheets, …) is made possible in a generic way using the two following properties: cosmetics.folder: This property points to a local folder on the controller’s host in which alternate cosmetic resources are stored (conf/cosmetics/ by default). cosmetics.interceptedResourceList: A comma-separated list of resources which are supposed to be replaces with custom resources. Defaults to step-variables. https://step.dev/knowledgebase/30/setup/configuration/maven-artifact-repository/ Sun, 23 Nov 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/maven-artifact-repository/ Artifact repositories configuration When deploying or executing Automation Packages and their libraries using maven coordinates, the artifacts are retrieved from the configured artifact repositories. The configuration is based on the standard maven settings.xml format and stored as a Step setting. Retrieve current maven settings You can get the current content of the maven settings.xml with following REST call: GET <controller-url>/rest/settings/maven_settings_default Modify maven settings You can invoke following service passing the content of your maven settings. https://step.dev/knowledgebase/30/setup/configuration/grid-proxy/ Wed, 10 Sep 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/setup/configuration/grid-proxy/ The Grid Proxy connects secondary Kubernetes clusters or namespaces that host agents (but not the controller or other Step services) to the primary Step grid. It forwards agent registration and execution traffic, and, when enabled, also manages dynamic agent provisioning. What is the Grid Proxy? The Grid Proxy is a Step component deployed in each secondary cluster (or namespace). It has two primary roles: 1. Agent connectivity The Grid Proxy forwards registration requests from the agents in the secondary cluster to the agent grid of the primary cluster (running in the controller). https://step.dev/knowledgebase/30/setup/configuration/jkskeystore/ Tue, 06 Apr 2021 00:00:00 +0100 https://step.dev/knowledgebase/30/setup/configuration/jkskeystore/ Both the controller, for its web application, and the agent, for the agent services, support SSL and require a Java KeyStore in JKS format for the certificates and keys. This short tutorial will show you how to generate a KeyStore in JKS format based on .key and .crt files. To generate it, you will need : the private key used to create your certificate request (.key file) the private key password (if any) the certificate generated with the previously transmitted certificate request (the . https://step.dev/knowledgebase/30/setup/configuration/encryption-manager/ Tue, 06 Apr 2021 00:00:00 +0100 https://step.dev/knowledgebase/30/setup/configuration/encryption-manager/ The encryption manager is a central component that provides encryption services for Step components that need to store sensitive values (like credentials for instance). The encryption manager is for instance used by the parameter module to store protected parameters. Enable the encryption manager The encryption manager can be enabled from the step.properties with the following property: plugins.EncryptionManagerControllerPlugin.enabled=true When starting a controller with the encryption manager the first time, a new RSA key pair will be generated and stored under the folder bin/encryptionManager.