[MXS-760] Allow different sets of users on backend servers Created: 2016-06-09  Updated: 2022-07-06  Resolved: 2019-10-10

Status: Closed
Project: MariaDB MaxScale
Component/s: Core, readwritesplit, schemarouter
Affects Version/s: None
Fix Version/s: 2.5.0

Type: New Feature Priority: Major
Reporter: David Cigánek Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MXS-2964 Enable schema router to handle distin... Closed
Epic Link: Router Improvements
Sprint: 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.



 Comments   
Comment by markus makela [ 2019-10-10 ]

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.

Generated at Thu Feb 08 04:01:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.