libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

RHSSO 602 updates

Browse source
This commit is contained in:
Chuck Copello 2016-12-05 14:32:49 -05:00
parent 1248c80134
commit b89d73530b
4 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
topics/authentication/otp-policies.adoc
View file

@ -29,7 +29,7 @@ versions of {{book.project.name}} it is planned that you will be able to configu
==== TOTP Configuration Options
OTP Hashing Algorithm::
OTP Hash Algorithm::
Default is SHA1, more secure options are SHA256 and SHA512.
Number of Digits::
How many characters is the OTP? Short means more user friendly as it is less the user has to type. More means more security.
@ -43,7 +43,7 @@ OTP Token Period::
==== HOTP Configuration Options
OTP Hashing Algorithm::
OTP Hash Algorithm::
Default is SHA1, more secure options are SHA256 and SHA512.
Number of Digits::
How many characters is the OTP? Short means more user friendly as it is less the user has to type. More means more security.

5
topics/export-import.adoc
View file

@ -94,8 +94,9 @@ Import of most resources can be performed from the admin console.
Exporting resources will be supported in future versions.
The files created during a "startup" export can be used to import from the admin UI.
This way, you can export from one realm and import to another realm. Note: The admin console import allows just one realm per file.
Or, you can export from one server and import to another.
This way, you can export from one realm and import to another realm. Or, you can export from one server and import to another.
Note: The admin console import allows just one realm per file.
WARNING: The admin console import allows you to "overwrite" resources if you choose.
Use this feature with caution, especially on a production system.

2
topics/overview/concepts.adoc
View file

@ -34,7 +34,7 @@ realms::
clients::
Clients are entities that can request {{book.project.name}} to authenticate a user. Most often, clients are applications and services that
want to use {{book.project.name}} to secure themselves and provide a single sign-on solution. Clients can also be entities that just want to request
identity information or an access token so that they can securely invoke other services on the network that are secured by {{book.project.name}}
identity information or an access token so that they can securely invoke other services on the network that are secured by {{book.project.name}}.
client adapters::
Client adapters are plugins that you install into your application environment to be able to communicate and be secured by {{book.project.name}}. {{book.project.name}}
has a number of adapters for different platforms that you can download. There are also third-party adapters you can get for environments that we don't cover.

2
topics/realms/keys.adoc
View file

@ -78,7 +78,7 @@ keys will no longer be active and can only be used for verifying signatures.
Locate the keypair in `Active` or `All` then click on the provider in the `Provider` column. This will take you to the
configuration screen for the key provider for the keys. Click on `Enabled` to turn it `OFF`, then click on `Save`. The
keys will no longer be active and can only be used for verifying signatures.
keys will no longer be enabled.
Alternatively, you can delete the provider from the `Providers` table.