-
Notifications
You must be signed in to change notification settings - Fork 88
Managing Secure Properties
The Zowe Secure Credential Store (SCS) plug-in has been integrated into the Imperative framework. The installation of a separate plug-in is no longer required. See the section named Remove unused artifacts from a previous zowe-v1-lts release within the document Working with Team Configuration. The inclusion of the secure credential store enables Zowe commands to automatically store sensitive values securely.
When profile properties are defined as secure and they are defined for inclusion in a team config template, Zowe commands ensure that those properties will be securely stored.
When you first run the zowe config init --global
command, the user and password properties for the "my_base" profile are included in the "secure" array within the team configuration file that is generated by the "config init" command. The "config init" command also prompts the user for that user name and password, but those values are never stored in the team config file. Those values are automatically stored within the secure storage mechanism of your operating system.
You can use an editor to manually add new profile properties to the secure array in zowe.config.json
. Any property that you define in the secure array will then also be stored only in the secure storage of your operating system.
You can issue the zowe config secure
command to re-prompt for all secure fields when you want to update them. You might use this command after you have added new secure fields. You might use this command when your organization requires you to change your password.
You can also secure a specific property. Use the command zowe config set --secure <property-path>
. For example, you can issue zowe config set --secure profiles.my_base.properties.password
. You will be prompted for the value of the property. If that property had already been secured, the value that you enter will replace the previous value in the secure credential store.
The Zowe Imperative framework interfaces with the npm package @zowe/secrets-for-zowe-sdk to store any profile properties marked as secure.
-
Core Features
- Imperative Configuration
- Defining Commands
- Command Handlers
- Command Option Precedence
- Environment Variables
- Help Generator
- Experimental Commands
- Creating Commands Using Chained Handlers
- Configuring Logging
- Working with Team Configuration
- Defining and Programming Profiles
- Managing Secure Properties
- Deprecated User Profiles
- Consuming REST APIs Using the REST Client
- Implementing Progress Bars
- Plugins