Some specific information on how dynamic configuration
changes impact security on the Liberty profile is introduced in this
topic.
Dynamically changing the user registry
Changing
the user registry can impact both the server configuration and clients
using the server. Before you change the user registry dynamically
(without restarting the server), consider the following:
- If you change the user registry type or realm name, all web clients
must clear their single sign-on tokens.
- If you change the user registry type or realm name, any values
of accessId that are specified in the authorization
bindings must be updated. The accessId takes
the form of user:realmName/uniqueId or group:realmName/uniqueId.
The realmName in the accessId must
match the realmName for the configuration user
registry.