Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
MXS-SPRINT-92
Description
It would be great to allow each server to have its own users, which could authenticate only to this particular server. Currently every new connection is authenticated against all backend servers.
I can see many use cases that would benefit from this feature, for example:
Creating a cluster from completely independent db servers
- one or more Maxscale instances as entry points
- every backend server has its own users and databases
- migration of any database (with its own users) between backends
- scallability: more backend servers can be added and populated with existing or new databases
Main advantage is that you can migrate databases between backend servers without changing hostname of the database and connection strings in applications.
Attachments
Issue Links
- is duplicated by
-
MXS-2964 Enable schema router to handle distinct sets of user accounts on database servers.
-
- Closed
-
Authentication failure are now handled on the router level. This allows use of clusters with a different set of users on some databases and it also prevents a complete service outage when a corrupted slave server denies access for some user.