hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update the user credential cache documentation

Browse Source 
The release notes now mention that the caching is done by the
authenticators, not by the core. It also mentions that only MySQLAuth
implements this functionality.

Added notes to binlogrouter documentation about the changes to the loading
and storing of users.

Cleaned up MySQL-Authenticator document to make it a bit easier to read.
This commit is contained in:
Markus Makela
2016-10-21 16:26:11 +03:00
parent aa20385347
commit c915ea71aa
3 changed files with 31 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md
View File

@ -47,6 +47,11 @@ For more information about this configuration entry, please see
### User data cache
The user data cache stores the cached credentials that are used by some router
modules. In 2.1.0, the authenticator modules are responsible for the persisting
of the user data cache. Currently, only the MySQLAuth module implements user
data caching.
The user data loaded from the backend databases is now stored on a per listener
basis instead of a per service basis. In earlier versions, each service had its own
cache directory in `/var/cache/maxscale`. This directory contains cached user