I have a database that I want to be able to allow users to connect to. I didn't design this database, just trying to come up with a way to allow users to connect. The way they set this database up is that there are three users, Read, Read/write, and Admin. What I have done is write a tool that can authenticate a specific user such as jsmith234, he's a member of the Admin team, when using my cli tool it logs jsmith in using the admin user of the database. JDoe432 is a member of the read group, only gets read access, when they run the tool, the tool logs the user in with read-only access.
Users can query the database, get into a mysql shell, dump the database, restore the database, save tables as excel, or csv -- but only from the command line. What my users want to do is be able to use tools like mysql workbench. I don't want to give them the database passwords as then you're constantly getting emails with people asking for the right creds, then you've got to look them up, give them the right user which is a pain. I don't want to get into what happens when we reset the password which by corporate standards is every 90 days. Currently I only have to change it in the database and in my tool. My question is if there is a way to write a middleware app that can be run, so that the user logs in with SSH, the tool authenticates them, and then starts a port forward back to their system allowing mysql workbench to connect. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/4f0c20c2-b866-495e-a78b-b03977a556b7n%40googlegroups.com.
