AM stores information about registered resources, audit information generated when users manage access to their protected resources, pending requests, and resource labels. AM stores these items in the configuration store by default.
For demo and test purposes, storing UMA information in the configuration store is sufficient and you do not need to take any additional action. To configure UMA for test purposes, see UMA use case.
For production environments, configure at least one external store to hold UMA information. Configure more stores to separate UMA objects in high-load deployments when data tuning requirements differ.
The tasks to configure UMA stores are: