## zowe › profiles › create › base-profile

Base profile that stores values shared by multiple service profiles

Warning: This command has been deprecated.
Recommended replacement: The 'config init' command

#### Usage

zowe profiles create base-profile <profileName> [options]

#### Positional Arguments

- `profileName` (string)

  - Specifies the name of the new base profile. You can load this profile by using the name on commands that support the "--base-profile" option.

#### Base Connection Options

- `--host` | `-H` (string)

  - Host name of service on the mainframe.

- `--port` | `-P` (number)

  - Port number of service on the mainframe.

- `--user` | `-u` (string)

  - User name to authenticate to service on the mainframe.

- `--password` | `--pass` | `--pw` (string)

  - Password to authenticate to service on the mainframe.

- `--reject-unauthorized` | `--ru` (boolean)

  - Reject self-signed certificates.

    Default value: true

- `--token-type` | `--tt` (string)

  - The type of token to get and use for the API. Omit this option to use the default token type, which is provided by 'zowe auth login'.

- `--token-value` | `--tv` (string)

  - The value of the token to pass to the API.

- `--cert-file` (local file path)

  - The file path to a certificate file to use for authentication.

    Note: The CLI does not support certificate files that require a password. For more information, search Troubleshooting PEM Certificates in Zowe Docs.

- `--cert-key-file` (local file path)

  - The file path to a certificate key file to use for authentication

#### Options

- `--overwrite` | `--ow` (boolean)

  - Overwrite the base profile when a profile of the same name exists.

- `--disable-defaults` | `--dd` (boolean)

  - Disable populating profile values of undefined properties with default values.

#### Examples

- Create a profile called 'base1' to connect to host example.com and port 443:

  - `zowe profiles create base-profile base1 --host example.com --port 443 --user admin --password 123456`

- Create a profile called 'base2' to connect to host example.com (default port - 443) and allow self-signed certificates:

  - `zowe profiles create base-profile base2 --host example.com --user admin --password 123456 --reject-unauthorized false`

- Create a profile called 'base3' to connect to host example.com and port 1443, not specifying a username or password so they are not stored on disk; these will need to be specified on every command:

  - `zowe profiles create base-profile base3 --host example.com --port 1443`

- Create a zosmf profile called 'base4' to connect to default port 443 and allow self-signed certificates, not specifying a username, password, or host so they are not stored on disk; these will need to be specified on every command:

  - `zowe profiles create base-profile base4 --reject-unauthorized false`