libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases 1 Packages Activity Actions

Merge pull request #101 from jenmalloy/RHSSO-942-take3

Browse source 
fixed remaining issues for RHSSO-942
This commit is contained in:
Jen Malloy 2017-04-05 16:33:28 -04:00 committed by GitHub
commit 9933c1d3de
4 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
server_development/topics/user-storage/cache.adoc
View file

@ -99,5 +99,5 @@ The `getCachedWith()` method returns a map that allows you to cache additional i
==== Cache Policies ==== 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.

2
server_development/topics/user-storage/migration.adoc
View file

@ -73,7 +73,7 @@ If you have implemented synchronization logic, then have your new `UserStoragePr
==== Upgrading to a New Model ==== 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 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 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. with the same provider ID (i.e., "ldap", "kerberos") as the earlier User Federation provider.

5
server_development/topics/user-storage/registration-query.adoc
View file

@ -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. 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 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.
doesn't support pagination, you'll have to do similar logic.
.PropertyFileUserStorageProvider .PropertyFileUserStorageProvider
[source,java] [source,java]

2
server_development/topics/user-storage/rest.adoc
View file

@ -10,7 +10,7 @@ The REST Component API lives under your realm admin resource.
/admin/realms/{realm-name}/components /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] [source,java]
---- ----