search

erlio / vmq_pgauth_demo

VerneMQ Demo Postgres Auth Plugin
5 stars 1 forks source link

Production Use #1

Open testark opened 8 years ago

testark commented 8 years ago

From the README:

This is for demonstration purposes only, as it currently doesn't deal with neither SQL injection, hashing of passwords, query result caching nor other issues related to production use.

Could you please point out what those "other issues" are? We are planning to use this in production and can deal with the first three, but as we're no Erlang experts we'd like to know what other issues we'd have to deal with.

dergraf commented 8 years ago

If you authorize every publish and your clients are publishing at a very high rate you certainly want to cache those SQL results. However if you have mainly longlived connections with only few publishes the plugin fuctionality could be enough. For a production setup I would improve the operation layer, so that you could easyer upgrade to new dbs or schemas... but yeah you could just as well use this and improve it the way along. Just please ensure that no client data directly makes its way to the SQL statement. Hope this helps! Am 17.11.2015 17:02 schrieb "testark" notifications@github.com:

From the README:

This is for demonstration purposes only, as it currently doesn't deal with neither SQL injection, hashing of passwords, query result caching nor other issues related to production use.

Could you please point out what those "other issues" are? We are planning to use this in production and can deal with the first three, but as we're no Erlang experts we'd like to know what other issues we'd have to deal with.

— Reply to this email directly or view it on GitHub https://github.com/erlio/vmq_pgauth_demo/issues/1.