sagcc add security credentials

Edit online

Adds security credentials for an installation or run-time component. Command Central does not store security credentials for run-time components. Command Central only stores the credentials it uses to connect to Platform Manager nodes. When adding security credentials for all run-time components, Command Central propagates the credentials to the run-time component installation. Command Central does not propagate only the credentials for the connection between Command Central and the Platform Manager installation.

Syntax

Command Central syntax:

With parameters

sagcc add security credentials  nodeAlias=node_alias            
[runtimeComponentId=componentid]   
authenticationType={NONE|BASIC|TRUSTED}  [username=username]   
[password=password]   [credentials=credentialsAlias]  [options]

With input file

sagcc add security credentials  nodeAlias=node_alias            
[runtimeComponentId=componentid]  {--input | -i} file{.xml|.json}        
[options]

         
 options:            
[{--debug | -d}]            
[{--error | -r} file]            
[{--log | -l} file]            
[{--password | -p} password]            
[{--quiet | -q}]            
[{--server | -s} url]]            
[{--username | -u} user_name]

Not supported by Platform Manager

Arguments and Options

Argument or Option	Description
`nodeAlias=node_alias`	Required. Specifies the alias name of the installation for which you want to associate the security credentials. You can view a list of installations and their aliases using sagcc list landscape nodes.
`[runtimeComponentId=componentid]`	Optional. Specifies the run-time component for which you want to associate the security credentials. You can determine the IDs for run-time components using sagcc list inventory components. Important: When configuring the credentials used for communication between Command Central and the Platform Manager installation, set this argument as follows: `runtimeComponentId=SPM-CONNECTION`.
`authenticationType={NONE\|BASIC\|TRUSTED}`	Required when you use the command syntax with parameters. Specifies the authentication type to use for the run-time component. Valid values: `NONE` `BASIC` - use basic authentication `TRUSTED` - use trusted authentication
`[username=username]`	Optional. Specifies the user name to use when the authentication type is set to `BASIC`.
`[password=password]`	Optional. Specifies the password to use when the authentication type is set to `BASIC`.
`[credentials=credentialsAlias]`	Optional. The alias of the COMMON-CREDENTIALS configuration instance that has the username/password that matches a set of user credentials, such as repository or product credentials.
`{--input \| -i} file{.xml\|.json}`	Required when you use the command syntax with input file. Identifies an input file that contains the data for the security credentials. For more information, see input. Tip: To determine how to specify the data in the input file, use sagcc get security credentials to retrieve data for existing security credentials. For example, if you want to use an XML input file, use sagcc get security credentials with the `--format xml` option to retrieve the data in XML format.
`[options]`	Optional. Refer to the command syntax for a list of the options the command supports. For a description of the options, see Common Options.

Usage Notes

By default, if you omit an argument, the command applies the credentials to all items. For example, if you omit the [runtimeComponentId=componentid] argument, the command applies the credentials to all run-time components.
When configuring the credentials used for communication between Command Central and the Platform Manager installation, you can specify either the username/password or a credentials alias defined for the Platform Manager installation as follows:
```
sagcc add security credentials nodeAlias=<nodeAlias> runtimeComponentId=SPM-CONNECTION 
{username=<user> password=<pass> | credentials=<credentialsAlias>}
```
You can set different credentials for the Platform Manager servers in your landscape using the Command Central web user interface or the command line tool. For example, you can configure Command Central to connect to one Platform Manager as “Administrator1/manage1” and the second Platform Manager server as “Administrator2/manage2”. For example:
```
sagcc add security credentials runtimeComponentId=SPM-CONNECTION        
nodeAlias=sag01 --input c:\inputs\creds_data.xml
```
Note: This command will not return an error. However, Command Central does not use the supplied credentials for connection to specified Platform Manager on the specified installation.

Examples When Executing on Command Central

In the following examples, because the {--server | -s} and {--username | -u} options are not specified, the commands use the default server and user name. For more information, see server and username. The commands specify “secret” for the user’s password.

To update the security credentials used for the communication between Command Central and the Platform Manager installed in the installation with alias name “sag01”, using authentication type “BASIC”:
```
sagcc add security credentials  nodeAlias=sag01            
runtimeComponentId=SPM-CONNECTION   
authenticationType=BASIC  username=Administrator  password=secret
```
To update the security credentials used for the communication between Command Central and the Platform Manager installed in the installation with alias name “sag01”, using an input file:
- After changing the Command Central default administrator password, create the c:\inputs\credentials_osgi.xml file. Open the credentials_osgi.xml file and include the updated security credentials for the run-time component with ID “SPM-CONNECTION”.
- Execute the following command:
```
sagcc add security credentials  nodeAlias=sag01     
runtimeComponentId=SPM-CONNECTION --input credentials_osgi.xml  
-p newpassword
```
To update the security credentials for a run-time component with ID “MwsProgramFiles” installed in the installation with alias name “sag01”, using trusted authentication:
```
sagcc add security credentials  nodeAlias=sag01            
runtimeComponentId=MwsProgramFiles   
authenticationType=TRUSTED
```

Security credentials data is in the c:\inputs\creds_data.xml file. To add security credentials for all Integration Server run-time components on all installations:

sagcc add security credentials runtimeComponentId=IntegrationServer_instanceName           
--input c:\inputs\creds_data.xml --password secret

Security credentials data is in the c:\inputs\creds_data.xml file. To add security credentials for the Integration Server run-time components on installations with alias names “sag01” and “sag02”, use the following two commands:

sagcc add security credentials nodeAlias=sag01           
runtimeComponentId=IntegrationServer_instanceName        
--input c:\inputs\creds_data.xml --password secret

sagcc add security credentials nodeAlias=sag02           
runtimeComponentId=IntegrationServer_instanceName        
--input c:\inputs\creds_data.xml --password secret