Merge pull request #101 from jenmalloy/RHSSO-942-take3
fixed remaining issues for RHSSO-942
This commit is contained in:
commit
9933c1d3de
4 changed files with 5 additions and 6 deletions
|
@ -99,5 +99,5 @@ The `getCachedWith()` method returns a map that allows you to cache additional i
|
|||
|
||||
==== Cache Policies
|
||||
|
||||
On the administration console management page for your user storage provider, you can specify a unique cache policy for each configured user storage provider.
|
||||
On the administration console management page for your user storage provider, you can specify a unique cache policy.
|
||||
|
||||
|
|
|
@ -73,7 +73,7 @@ If you have implemented synchronization logic, then have your new `UserStoragePr
|
|||
|
||||
==== Upgrading to a New Model
|
||||
|
||||
The User Storage SPI instances are stored in a completely different set of relational tables or Mongo schema. {{book.project.name}}
|
||||
The User Storage SPI instances are stored in a different set of relational tables. {{book.project.name}}
|
||||
automatically runs a migration script. If any earlier User Federation providers are deployed for a realm, they are converted
|
||||
to the later storage model as is, including the `id` of the data. This migration will only happen if a User Storage provider exists
|
||||
with the same provider ID (i.e., "ldap", "kerberos") as the earlier User Federation provider.
|
||||
|
|
|
@ -155,9 +155,8 @@ by our example provider. Let's look at implementing this interface.
|
|||
}
|
||||
----
|
||||
|
||||
The `getUser()` method simple iterates over the key set of the property file delegating to `getuserByUsername` to load a user.
|
||||
Notice that we are indexing this call based on the `firstResult` and `maxResults` parameter. If your external store
|
||||
doesn't support pagination, you'll have to do similar logic.
|
||||
The `getUser()` method iterates over the key set of the property file, delegating to `getUserByUsername()` to load a user.
|
||||
Notice that we are indexing this call based on the `firstResult` and `maxResults` parameter. If your external store does not support pagination, you will have to do similar logic.
|
||||
|
||||
.PropertyFileUserStorageProvider
|
||||
[source,java]
|
||||
|
|
|
@ -10,7 +10,7 @@ The REST Component API lives under your realm admin resource.
|
|||
/admin/realms/{realm-name}/components
|
||||
----
|
||||
|
||||
We will only show this REST API interaction with the Java client. Hopefully you can extract how to do this from curl from this API.
|
||||
We will only show this REST API interaction with the Java client. Hopefully you can extract how to do this from `curl` from this API.
|
||||
|
||||
[source,java]
|
||||
----
|
||||
|
|
Loading…
Reference in a new issue