From d1014006d41e6686280cad97e303c8c9c437b9e4 Mon Sep 17 00:00:00 2001 From: Bruno Oliveira da Silva Date: Thu, 29 Aug 2019 15:04:03 -0300 Subject: [PATCH] Fix sentence for KEYCLOAK-10734 based on feedback from #716 Co-authored-by: Andy Munro --- securing_apps/topics/oidc/javascript-adapter.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/securing_apps/topics/oidc/javascript-adapter.adoc b/securing_apps/topics/oidc/javascript-adapter.adoc index afc9cb58e3..7d822cc475 100644 --- a/securing_apps/topics/oidc/javascript-adapter.adoc +++ b/securing_apps/topics/oidc/javascript-adapter.adoc @@ -62,7 +62,7 @@ redirected back to the application and remain unauthenticated. You can configure a _silent_ `check-sso` option. With this feature enabled, your browser won't do a full redirect to the {project_name} server and back to your application, but this action will be performed in a hidden iframe, so your application resources only need to be loaded and parsed once by the browser when the app is initialized and not again after the redirect back from {project_name} to your app. -This is particular useful in case of SPAs (Single Page Applications). +This is particularly useful in case of SPAs (Single Page Applications). To enable the _silent_ `check-sso`, you have to provide a `silentCheckSsoRedirectUri` attribute in the init method. This URI needs to be a valid endpoint in the application (and of course it must be configured as a valid redirect for the client in the {project_name} Administration Console):