[MXS-673] Separate authentication form data Created: 2016-04-15 Updated: 2016-10-10 Resolved: 2016-10-10 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Marcin Stolarek | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
I'm wondering if it's possible to add an additional mechanism for authentication, for my current implementation it would be very nice to have simple file like user:password (or user:hash) that will perform authentication, and than limit access to data only with maxscale filters - without the need to keep users in mariadb databases. Maybe even more functional would be to integrate maxscale with pam, so I'll probably be able to allow acces on LDAP users in our office. |
| Comments |
| Comment by markus makela [ 2016-04-15 ] |
|
This can be achieved when the pluggable authentication is implemented. PAM is a good first candidate for an authentication plugin. |
| Comment by John W Smith [ 2016-08-19 ] |
|
This all relates to pluggable authentication being implemented. |
| Comment by markus makela [ 2016-10-10 ] |
|
Authentication is now modular in MaxScale. |