From 0bcf8bcc5e33d981b3a2a097150d11c0bbaa79f6 Mon Sep 17 00:00:00 2001 From: Andy Munro Date: Fri, 19 Feb 2021 15:24:57 -0500 Subject: [PATCH] Change i.e. to such as --- server_admin/topics/sessions/offline.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server_admin/topics/sessions/offline.adoc b/server_admin/topics/sessions/offline.adoc index 727e444ae4..32462c133f 100644 --- a/server_admin/topics/sessions/offline.adoc +++ b/server_admin/topics/sessions/offline.adoc @@ -18,4 +18,4 @@ Users can view and revoke offline tokens that {project_name} grants them in the To issue an offline token, users must have the role mapping for the realm-level `offline_access` role. Clients must also have that role in their scope. Clients must add an `offline_access` client scope as an `Optional client scope` to the role, which is done by default. -Clients can request an offline token by adding the parameter `scope=offline_access` when sending their authorization request to {project_name}. The {project_name} OIDC client adapter automatically adds this parameter when you use it to access your application's secured URL (i.e., $$http://localhost:8080/customer-portal/secured?scope=offline_access$$). The Direct Access Grant and Service Accounts support offline tokens if you include `scope=offline_access` in the authentication request body. +Clients can request an offline token by adding the parameter `scope=offline_access` when sending their authorization request to {project_name}. The {project_name} OIDC client adapter automatically adds this parameter when you use it to access your application's secured URL (such as, $$http://localhost:8080/customer-portal/secured?scope=offline_access$$). The Direct Access Grant and Service Accounts support offline tokens if you include `scope=offline_access` in the authentication request body.