we have ravendb server master-slave setup. there 1 master db documents written via 1 process, replicated slaves.
the slaves accessed via web application, make replicated documents read-only.
when looking security options, find @ db level , @ document level (using authorization bundle). first makes entire db read-only should not case. second convoluted , more fine-grained security don't need.
we hoping web application connect ravendb credentials context (not application users, system user website runs as), collections read-only identity. possible in sql server example.
any alternative solutions such replicating documents read-only appreciated. our current best idea have put triggers on server make required documents read-only on slave databases.
you can use api keys this: https://ravendb.net/docs/article-page/3.0/csharp/server/configuration/authentication-and-authorization#oauth-authentication
one api key (read/write) replication 1 api key (read only) application
Comments
Post a Comment