Fix sentence for KEYCLOAK-10734 based on feedback from #716

Co-authored-by: Andy Munro <amunro@redhat.com>
This commit is contained in:
Bruno Oliveira da Silva 2019-08-29 15:04:03 -03:00
parent 600d5ca66c
commit d1014006d4

View file

@ -62,7 +62,7 @@ redirected back to the application and remain unauthenticated.
You can configure a _silent_ `check-sso` option. 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. 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. 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): 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):