might want to put the password file(s) in /usr/local/apache/passwd. To create the file, use the htpasswd utility that came with Apache. This will be located in the bin directory of wherever you installed create the file, type: htpasswd -c /usr/local/apache/passwd/passwords rbowen httpswd will ask you for the password, and then ask you to type it again to confirm it: # htpasswd -c /usr/local/apache/passwd/passwords rbowen If htpasswd is not in your path, of course you'll have to type the full path to the file to get it to run. With a default installation, it's located at /usr/local/apache2/bin/htpasswd Next

to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway) • htpasswd now uses MD5 hash by default on all platforms. - The NameVirtualHost directive no longer has any configuration: /usr/local/apache/htdocs/.htpasswd As you can see, the log files only report what already has happened, so if the client had been able to access the .htpasswd file you would have seen something something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration file:

to HTTPS hosts with bad or outdated certificates to fail with a 502 status code (Bad gateway) • htpasswd now uses MD5 hash by default on all platforms. - The NameVirtualHost directive no longer has any May now create a link to the current log file. May now invoke a custom post-rotate script. ## htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later). ## Documentation ## mod_rewrite configuration: /usr/local/apache/htdocs/.htpasswd As you can see, the log files only report what already has happened, so if the client had been able to access the .htpasswd file you would have seen something

.... 26 6.4. 身份提供程序参数 ..... 26 6.5. 身份提供程序 CR 示例 ..... 27 第7章 配置身份提供程序 ..... 28 7.1. 配置 HTPASSWD 身份提供程序 ..... 28 7.2. 配置 KEYSTONE 身份提供程序 ..... 33 7.3. 配置 LDAP 身份提供程序 ..... 36 7.4. 配置基本身份验证身份提供程序 地主机中运行容器。 ## 自定义资源 (CR) CR 是 Kubernetes API 的扩展。 ## group 组是一组用户。组可用于一次性向多个用户授予权限。 ## HTPasswd htpasswd 更新存储 HTTP 用户验证的用户名和密码的文件。 ## Keystone Keystone 是一个 Red Hat OpenStack Platform (RHOSP) 项目 用户名不能包括 /、：和 %。 #### 6.2. 支持的身份提供程序 您可以配置以下类型的身份提供程序： |用户身份提供程序|描述| |---|---| |htpasswd|配置 htpasswd 身份提供程序，针对使用 htpasswd 生成的文件验证用户名和密码。| |Keystone|配置 keystone 身份提供程序，将 OpenShift Container Platform 集群与

configuration: /usr/local/apache/htdocs/.htpasswd As you can see, the log files only report what already has happened, so if the client had been able to access the .htpasswd file you would have seen something something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration file: might want to put the password file(s) in /usr/local/apache/passwd. To create the file, use the htpasswd utility that came with Apache. This will be located in the bin directory of wherever you installed

configuration: /usr/local/apache/htdocs/.htpasswd As you can see, the log files only report what already has happened, so if the client had been able to access the .htpasswd file you would have seen something something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration file: might want to put the password file(s) in /usr/local/apache/passwd. To create the file, use the htpasswd utility that came with Apache. This will be located in the bin directory of wherever you installed

DBM password databases 259 8.9 htdigest - manage user files for digest authentication 262 8.10 htpasswd - Manage user files for basic authentication 263 8.11 logresolve - Resolve IP-addresses to hostnames configuration: /usr/local/apache/htdocs/.htpasswd As you can see, the log files only report what already has happened, so if the client had been able to access the .htpasswd file you would have seen something something similar to: foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log (p. 29). This means you probably commented out the following in your server configuration

configuration: /usr/local/apache/htdocs/.htpasswd As you can see, the log files only report what already has happened, so if the client had been able to access the .htpasswd file you would have seen something something similar to: foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" in your Access Log. This means you probably commented out the following in your server configuration file: might want to put the password file(s) in /usr/local/apache/passwd. To create the file, use the htpasswd utility that came with Apache. This will be located in the bin directory of wherever you installed

databases ..... 289 8.10 htdigest - manage user files for digest authentication ..... 292 8.11 htpasswd - Manage user files for basic authentication ..... 293 8.12 httxt2dbm - Generate dbm files for might want to put the password file(s) in /usr/local/apache/passwd. To create the file, use the htpasswd utility that came with Apache. This will be located in the bin directory of wherever you installed create the file, type: htpasswd -c /usr/local/apache/passwd/passwords rbowen htpasswd will ask you for the password, and then ask you to type it again to confirm it: # htpasswd -c /usr/local/apache/passwd/passwords

OpenShift。 #### 3.2. 更改身份提供者中的日志 全新安装的 OpenShift Container Platform 实例的默认行为是拒绝任何用户登录。将验证方法改为 HTPasswd: 1. 以编辑模式打开 /etc/origin/master/master-config.yaml 文件。 2. 查找 identityProviders 部分。 3. 将 DenyA file: /etc/origin/master/htpasswd 5. 保存该文件。 #### 3.3. 创建用户帐户 现在，您已开始使用 HTPasswdPasswordIdentityProvider 身份验证机制，您需要生成相应的用户账户。 1. 您可以使用 httpd-tools 软件包来获得可生成这些帐户的 htpasswd 二进制文件。 # yum -y install httpd-tools httpd-tools 2. 创建用户帐户。 # touch /etc/origin/master/htpasswd # htpasswd -b /etc/origin/master/htpasswd admin redhat 您已创建了用户 admin，密码为 redhat。 ### 3. 在继续前重启 OpenShift。 # master-restart api # master-restart