Skip to content

Commit c25969e

Browse files
committed
rewrite SSO
1 parent 2a3bef6 commit c25969e

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

modules/rosa-configure.adoc

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,20 @@ Use the following commands to configure the {product-title} (ROSA) CLI, `rosa`.
1212
== login
1313
There are several methods you can use to log into your Red{nbsp}Hat account using the {product-title} (ROSA) CLI (`rosa`). These methods are described in detail below.
1414

15-
[IMPORTANT]
16-
====
17-
An offline authentication token is long-lived, stored on your operating system, and cannot be revoked. These factors increase overall security risks and the likelihood of unauthorized access to your account. Alternatively, the Red{nbsp}Hat secure browser-based single sign-on (SSO) method automatically sends your CLI instance a refresh token that is valid for 10 hours. Because this authorization code is unique and temporary, it is more secure and is the Red{nbsp}Hat recommended method of authentication.
18-
====
19-
20-
// Furthermore, offline authentication tokens are usually stored on your device by your operating system, which means other apps on your machine can access a token if the token is not properly secured. These offline tokens are long-lived and cannot be revoked. Users must copy and paste them manually which creates a security risk. Because of these factors, Red{nbsp}Hat recommends using the single sign-on method when logging into your account with the ROSA CLI (`rosa`). This method is more secure than logging in with an offline token.
15+
// [IMPORTANT]
16+
// ====
17+
// An offline authentication token is long-lived, stored on your operating system, and cannot be revoked. These factors increase overall security risks and the likelihood of unauthorized access to your account. Alternatively, the Red{nbsp}Hat secure browser-based single sign-on (SSO) method automatically sends your CLI instance a refresh token that is valid for 10 hours. Because this authorization code is unique and temporary, it is more secure and is the Red{nbsp}Hat recommended method of authentication.
2118
// ====
2219

2320

2421
[id="rosa-login-sso_{context}"]
25-
=== login with single sign-on (SSO) authorization code
22+
=== Authenticating the {product-title} (ROSA) CLI with Red Hat Single Sign-On
23+
24+
If your system supports a web-based browser, you can log in to the ROSA CLI (`rosa`) with a Red{nbsp}Hat single sign-on (SSO) authorization code. Red{nbsp}Hat recommends using the ocm-cli command line tool with Red{nbsp}Hat single Sign-On, instead of using an offline authentication token.
25+
26+
An offline authentication token is long-lived, stored on your operating system, and cannot be revoked. These factors increase overall security risks and the likelihood of unauthorized access to your account. Alternatively, the Red Hat secure browser-based single sign-on (SSO) method automatically sends your CLI instance a refresh token that is valid for 10 hours. Because this authorization code is unique and temporary, it is more secure and is the Red Hat recommended method of authentication.
27+
2628

27-
If your system supports a web-based browser, you can log in to the ROSA CLI (`rosa`) with a Red{nbsp}Hat single sign-on (SSO) authorization code.
2829

2930
[NOTE]
3031
====

0 commit comments

Comments
 (0)