Server Dev Guide: QE review issues part 3

From Tomas Kyjovsky:

5.7.2
p2:
The getUser() method simple iterates the key set of the property file delegating to
getuserByUsername to load a user
-->
The getUser() method simply iterates over the key set of the property file delegating to
getUserByUsername() to load a user

p3:
paraeter --> parameter

p5:
We don’t store and groups or attributes

5.9
p1:
built in user database --> built-in user database

5.9.1.
p2:
user exists still --> user still exists

5.9.2.
p1:
it would be possible for the local user copy could to get out of sync

5.10.3.
Each configured user storage provider can specify unique cache policies. Go to the admin console
management page for your provider to see how to do this.
--->
It is possible to specify a unique cache policy for each configured user storage provider. This can be done on the admin console
management page for your provider.

5.11.
warning note:
server will barf with show an error message

5.12.
Hopefully you can extract how do do this from curl from this api API.

5.13.2.
p2:
— problem with formatting/font

5.13.4.
The User Storage SPI instances are stored in a completely different set of relational tables or
Mongo schema. — afaik Mongo is not supported in product, Mongo libraries are not present