Skip to content

Commit be65077

Browse files
authored
Merge pull request #42822 from pneedle-rh/osdocs-2943-update-htpasswd-description
OSDOCS-2943 - Updating the HTPasswd IDP description in the SD docs
2 parents 6bdbd1e + c6a804e commit be65077

File tree

6 files changed

+72
-29
lines changed

6 files changed

+72
-29
lines changed

modules/config-htpasswd-idp.adoc

Lines changed: 45 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,37 @@
11
// Module included in the following assemblies:
22
//
3+
// * rosa_getting_started/rosa-sts-config-identity-providers.adoc
4+
// * rosa_getting_started/rosa_getting_started_iam/rosa-config-identity-providers.adoc
35
// * identity_providers/config-identity-providers.adoc
46

7+
ifeval::["{context}" == "config-identity-providers"]
8+
:osd-distro:
9+
endif::[]
10+
ifeval::["{context}" == "rosa-sts-config-identity-providers"]
11+
:rosa-distro:
12+
endif::[]
13+
ifeval::["{context}" == "rosa-config-identity-providers"]
14+
:rosa-distro:
15+
endif::[]
16+
517
:_content-type: PROCEDURE
618
[id="config-htpasswd-idp_{context}"]
719
= Configuring an HTPasswd identity provider
820

921
Configure an HTPasswd identity provider to create a single, static user with cluster administration privileges. You can log in to your cluster as the user to troubleshoot issues.
1022

23+
[IMPORTANT]
24+
====
25+
The HTPasswd identity provider option is included only to enable the creation of a single, static administration user. HTPasswd is not supported as a general-use identity provider for {product-title}.
26+
====
27+
1128
.Procedure
1229

13-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you need to configure identity providers for.
30+
. From {cluster-manager-url}, navigate to the *Clusters* page and select your cluster.
1431

15-
. Click the *Access control* tab.
32+
. Select *Access control* -> *Identity providers*.
1633

1734
. Click *Add identity provider*.
18-
+
19-
[NOTE]
20-
====
21-
You can also click the *Add Oauth configuration* link in the warning message displayed after cluster creation to configure your identity providers.
22-
====
2335

2436
. Select *HTPasswd* from the *Identity Provider* drop-down menu.
2537

@@ -29,26 +41,40 @@ You can also click the *Add Oauth configuration* link in the warning message dis
2941
+
3042
[NOTE]
3143
====
32-
The credentials defined in this step are not visible after you select *Confirm* in the following step. If you lose the credentials, you must recreate the identity provider and define the credentials again.
44+
The credentials defined in this step are not visible after you select *Add* in the following step. If you lose the credentials, you must recreate the identity provider and define the credentials again.
3345
====
3446

35-
. Select *Confirm* to create the HTPasswd identity provider and the user.
47+
. Select *Add* to create the HTPasswd identity provider and the single, static user.
3648

3749
. Grant the static user permission to manage the cluster:
38-
.. Select *Add user* in the *Cluster administrative users* section of the *Access control* page.
39-
.. Enter the username that you defined in the preceding step into the *User ID* field.
40-
.. Select *Add user* to grant standard administration privileges to the user.
41-
+
42-
[NOTE]
43-
====
44-
The user is added to the `dedicated-admins` group.
45-
====
50+
.. Under *Access control* -> *Cluster Roles and Access*, select *Add user*.
51+
.. Enter the *User ID* of the static user that you created in the preceding step.
52+
ifdef::osd-distro[]
53+
.. Select a *Group.*
54+
** If you are installing {product-title} using the Customer Cloud Subscription (CCS) infrastructure type, choose either the `dedicated-admins` or `cluster-admins` group. Users in the `dedicated-admins` group have standard administrative privileges for {product-title}. Users in the `cluster-admins` group have full administrative access to the cluster.
55+
** If you are installing {product-title} using the Red Hat cloud account infrastructure type, the `dedicated-admins` group is automatically selected.
56+
endif::osd-distro[]
57+
ifdef::rosa-distro[]
58+
.. Select a *Group*. Users in the `dedicated-admins` group have standard administrative privileges for {product-title}. Users in the `cluster-admins` group have full administrative access to the cluster.
59+
endif::rosa-distro[]
60+
.. Select *Add user* to grant the administration privileges to the user.
4661

4762
.Verification
4863

49-
* The configured identity provider is now visible on the *Access control* tab of the *Clusters* page.
64+
* The configured HTPasswd identity provider is visible on the *Access control* -> *Identity providers* page.
5065
+
5166
[NOTE]
5267
====
53-
After creating the identity provider, synchronization usually completes within two minutes. You can login to the cluster as the user after the HTPasswd identity provider becomes available.
68+
After creating the identity provider, synchronization usually completes within two minutes. You can log in to the cluster as the user after the HTPasswd identity provider becomes available.
5469
====
70+
* The single, administrative user is visible on the *Access control* -> *Cluster Roles and Access* page. The administration group membership of the user is also displayed.
71+
72+
ifeval::["{context}" == "config-identity-providers"]
73+
:!osd-distro:
74+
endif::[]
75+
ifeval::["{context}" == "rosa-sts-config-identity-providers"]
76+
:!rosa-distro:
77+
endif::[]
78+
ifeval::["{context}" == "rosa-config-identity-providers"]
79+
:!rosa-distro:
80+
endif::[]

modules/config-idp.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
// Module included in the following assemblies:
22
//
3-
// * assemblies/osd-quickstart.adoc
3+
// * osd_quickstart/osd-quickstart.adoc
44

55
:_content-type: PROCEDURE
66
[id="config-idp_{context}"]
@@ -10,6 +10,11 @@ After you have installed {product-title}, you must configure your cluster to use
1010

1111
You can configure different identity provider types for your {product-title} cluster. Supported types include GitHub, GitHub Enterprise, GitLab, Google, LDAP, OpenID Connect, and HTPasswd identity providers.
1212

13+
[IMPORTANT]
14+
====
15+
The HTPasswd identity provider option is included only to enable the creation of a single, static administration user. HTPasswd is not supported as a general-use identity provider for {product-title}.
16+
====
17+
1318
The following procedure configures a GitHub identity provider as an example.
1419

1520
[WARNING]

modules/rosa-getting-started-configure-an-idp.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,12 @@
66
[id="rosa-getting-started-configure-an-idp_{context}"]
77
= Configuring an identity provider
88

9-
You can configure different identity provider types for your {product-title} (ROSA) cluster. Supported types include GitHub, GitHub Enterprise, GitLab, Google, LDAP, OpenID Connect and HTPassword identity providers.
9+
You can configure different identity provider types for your {product-title} (ROSA) cluster. Supported types include GitHub, GitHub Enterprise, GitLab, Google, LDAP, OpenID Connect and HTPasswd identity providers.
10+
11+
[IMPORTANT]
12+
====
13+
The HTPasswd identity provider option is included only to enable the creation of a single, static administration user. HTPasswd is not supported as a general-use identity provider for {product-title}.
14+
====
1015

1116
The following procedure configures a GitHub identity provider as an example.
1217

modules/understanding-idp.adoc

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
// Module included in the following assemblies:
22
//
3+
// * rosa_getting_started/rosa-sts-config-identity-providers.adoc
4+
// * rosa_getting_started/rosa_getting_started_iam/rosa-config-identity-providers.adoc
35
// * identity_providers/config-identity-providers.adoc
4-
// * rosa_getting_started/rosa-config-identity-providers.adoc
5-
// * rosa_getting_started_sts/rosa-sts-config-identity-providers.adoc
66

77
:_content-type: CONCEPT
88
[id="understanding-idp_{context}"]
@@ -22,22 +22,27 @@ You can configure the following types of identity providers:
2222
|Description
2323

2424
|GitHub or GitHub Enterprise
25-
|Configure a `github` identity provider to validate usernames and passwords against GitHub or GitHub Enterprise's OAuth authentication server.
25+
|Configure a GitHub identity provider to validate usernames and passwords against GitHub or GitHub Enterprise's OAuth authentication server.
2626

2727
|GitLab
28-
|Configure a `gitlab` identity provider to use link:https://gitlab.com/[GitLab.com] or any other GitLab instance as an identity provider.
28+
|Configure a GitLab identity provider to use link:https://gitlab.com/[GitLab.com] or any other GitLab instance as an identity provider.
2929

3030
|Google
31-
|Configure a `google` identity provider using link:https://developers.google.com/identity/protocols/OpenIDConnect[Google's OpenID Connect integration].
31+
|Configure a Google identity provider using link:https://developers.google.com/identity/protocols/OpenIDConnect[Google's OpenID Connect integration].
3232

3333
|LDAP
34-
|Configure the `ldap` identity provider to validate usernames and passwords against an LDAPv3 server, using simple bind authentication.
34+
|Configure an LDAP identity provider to validate usernames and passwords against an LDAPv3 server, using simple bind authentication.
3535

3636
|OpenID Connect
37-
|Configure an `oidc` identity provider to integrate with an OpenID Connect identity provider using an link:http://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth[Authorization Code Flow].
37+
|Configure an OpenID Connect (OIDC) identity provider to integrate with an OIDC identity provider using an link:http://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth[Authorization Code Flow].
3838

3939
|HTPasswd
40-
|Configure an `htpasswd` identity provider for a single, static administration user. You can log in to the cluster as the user to troubleshoot issues.
40+
|Configure an HTPasswd identity provider for a single, static administration user. You can log in to the cluster as the user to troubleshoot issues.
41+
42+
[IMPORTANT]
43+
====
44+
The HTPasswd identity provider option is included only to enable the creation of a single, static administration user. HTPasswd is not supported as a general-use identity provider for {product-title}. For the steps to configure the single user, see _Configuring an HTPasswd identity provider_.
45+
====
4146

4247
|===
4348

rosa_getting_started/rosa-sts-config-identity-providers.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ include::modules/config-gitlab-idp.adoc[leveloffset=+1]
1616
include::modules/config-google-idp.adoc[leveloffset=+1]
1717
include::modules/config-ldap-idp.adoc[leveloffset=+1]
1818
include::modules/config-openid-idp.adoc[leveloffset=+1]
19+
include::modules/config-htpasswd-idp.adoc[leveloffset=+1]
1920

2021
[id="additional-resources-cluster-access-sts"]
2122
[role="_additional-resources"]

rosa_getting_started/rosa_getting_started_iam/rosa-config-identity-providers.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ include::modules/config-gitlab-idp.adoc[leveloffset=+1]
1616
include::modules/config-google-idp.adoc[leveloffset=+1]
1717
include::modules/config-ldap-idp.adoc[leveloffset=+1]
1818
include::modules/config-openid-idp.adoc[leveloffset=+1]
19+
include::modules/config-htpasswd-idp.adoc[leveloffset=+1]
1920

2021
[id="additional-resources-idps"]
2122
[role="_additional-resources"]

0 commit comments

Comments
 (0)