Skip to content

Commit d82fe22

Browse files
committed
rewrite SSO
1 parent ffec83d commit d82fe22

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

modules/rosa-configure.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,19 @@ 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
// ====
22-
2319

2420
[id="rosa-login-sso_{context}"]
25-
=== login with single sign-on (SSO) authorization code
21+
=== Authenticating the {product-title} (ROSA) CLI with Red Hat Single Sign-On
22+
23+
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 `rosa` command line tool with Red{nbsp}Hat single Sign-On, instead of using an offline authentication token.
24+
25+
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, authenticating with the Red{nbsp}Hat 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 less likely to be used for unauthorized access to your account.
26+
2627

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.
2828

2929
[NOTE]
3030
====

0 commit comments

Comments
 (0)