| //// |
| Licensed to the Apache Software Foundation (ASF) under one |
| or more contributor license agreements. See the NOTICE file |
| distributed with this work for additional information |
| regarding copyright ownership. The ASF licenses this file |
| to you under the Apache License, Version 2.0 (the |
| "License"); you may not use this file except in compliance |
| with the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, |
| software distributed under the License is distributed on an |
| "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| KIND, either express or implied. See the License for the |
| specific language governing permissions and limitations |
| under the License |
| //// |
| |
| `password`:: The password to unlock the private key. You do not need to specify this if the private key does not have a password. By using different prefixes, you can specify the password several different ways depending on your security requirements: |
| + |
| * Specify the absolute path to a file that contains the password. This is the most secure option, because you can set permissions on the file that contains the password. For example: |
| + |
| [options="nowrap",subs="+quotes"] |
| ---- |
| password: file:/etc/pki/tls/private/password.txt |
| ---- |
| |
| * Specify an environment variable that stores the password. Use this option with caution, because the environment of other processes is visible on certain platforms. For example: |
| + |
| [options="nowrap",subs="+quotes"] |
| ---- |
| password: env:CERT_PASSWORD |
| ---- |
| |
| * Specify the password in clear text. This option is insecure, so it should only be used if security is not a concern. For example: |
| + |
| [options="nowrap",subs="+quotes"] |
| ---- |
| password: pass:mycertpassword |
| ---- |
