https://step.dev/knowledgebase/31/categories/security/ Recent content in Security on Step Documentation Hugo -- gohugo.io en Tue, 29 Sep 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/setup/configuration/identity-management/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/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/31/setup/configuration/ssl-settings/ Thu, 08 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/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/31/setup/download/material_request/ Mon, 29 Nov 2021 14:08:01 +0100 https://step.dev/knowledgebase/31/setup/download/material_request/ Enterprise customer credentials Enterprise customers receive their credentials to access to the Step Enterprise artifacts (Enterprise release, Docker images and Helm Chart) from the Step support upon request. Main point of contact for any issue related to access request is support@exense.ch. Nexus and Docker private repository Nexus access Step Enterprise artifacts are now published to our Nexus in the ‘distribution’ repository. The Enterprise repository can be accessed via https, preferably using a Web browser at https://nexus-enterprise. https://step.dev/knowledgebase/31/ai/step-agent/data-privacy/ Tue, 29 Sep 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/ai/step-agent/data-privacy/ The Step AI Agent calls a large language model (LLM) as part of producing automation packages. Content from the application under test therefore reaches a model by design. This page states what does, what does not, and what you decide. Unlike the Step MCP Server, which never calls a model itself and leaves that choice to your own AI assistant, the agent makes those calls within its workflow. What leaves your environment While producing automation, the agent sends to the model: https://step.dev/knowledgebase/31/userdocs/parameters/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/parameters/ Parameters are centrally defined variables that can be accessed by both Keywords and Plans in Step. They offer several key capabilities: Scope Assignment: Parameters can be assigned to specific scopes, restricting their visibility and access to certain applications or keywords. Protection of Sensitive Parameters: Sensitive parameters can be protected to hide their values from users, ensuring secure handling of critical data. Activation Expressions: Parameters can be dynamically assigned or mapped to specific environments, users, or other conditions using activation expressions. https://step.dev/knowledgebase/31/admindocs/role-management/ Mon, 17 Oct 2022 14:25:01 +0100 https://step.dev/knowledgebase/31/admindocs/role-management/ General concepts Every Step user is assigned a main role upon creation. With the default configuration of roles and rights, only users with the admin role can access Step projects without any further action. Users with other roles need to be added as members of specific projects; for each project membership, a specific role is defined. Role management is only available in the Enterprise Edition of Step. Pre-populated Roles Role Definition guest grants read-only access while preventing modifications or executions tester grants most privileges required to define and execute test plans developer in addition to tester rights, grants the ability to define keywords and administer individual projects admin grants all privileges Default access matrix By default, the following mapping of roles and rights is provided. https://step.dev/knowledgebase/31/admindocs/projectmanagement/ Thu, 05 Dec 2019 14:25:01 +0100 https://step.dev/knowledgebase/31/admindocs/projectmanagement/ Multitenancy and project management helps isolating and managing assets (such as Plans, Keywords, Executions, etc) throughout the application. The main benefits of working with projects is the ability to serve multiple tenants and/or group of users with a single instance of Step facilitating the organization of your work and improving security. Except for administrators, user must be assigned to at least one project to be able to work with step. https://step.dev/knowledgebase/31/userdocs/userpreferences/ Sun, 29 Nov 2020 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/userpreferences/ User Settings Credentials and preferences can be defined from the User Settings page. Click on your username on the top right box, then on “User Settings”: User Credentials and API keys On the “User Settings”, you can modify your password as well as generate and revoke Api keys. Generate an API Key API keys are used to authenticate with Step when accessing the Step API, whether through direct REST calls, the Step client, or the CLI. https://step.dev/knowledgebase/31/setup/configuration/grid-proxy/ Wed, 10 Sep 2025 00:00:00 +0000 https://step.dev/knowledgebase/31/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/31/setup/configuration/jkskeystore/ Tue, 06 Apr 2021 00:00:00 +0100 https://step.dev/knowledgebase/31/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/31/setup/configuration/encryption-manager/ Tue, 06 Apr 2021 00:00:00 +0100 https://step.dev/knowledgebase/31/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. https://step.dev/knowledgebase/31/admindocs/ Thu, 28 Mar 2019 00:00:00 +0000 https://step.dev/knowledgebase/31/admindocs/ This space is dedicated to the administration and operation of Step. For the installation of Step follow the set up documentation.