Proposed Admin DB #5807
ehuelsmann
started this conversation in
Design
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
(originally posted on the wiki by @sbts )
Brief
This proposal is to add an Admin DB that is used to maintain
Detail
This facilitates a variety of enhancements in UX and security
We'd still allow company selection via URL param so bookmarks etc could be company specific for login.
If doing that redirect it would be via a warning page explaining this is a first time setup thing and normally you need to use the setup url for admin
A completed and authenticated login is required first (after all we are authenticating against a role so we should be able to login without specifying a company db.
Once the login is authenticated then the admin db is queried for what companies are available to the authorised user
Security Implications
(provide access to "public" information such as what port an instance will run on.)
Affected Workflows
I think these workflows would move to the admin DB.
for this I'd think it just becomes an additional layer. ie: we first load defaults, then the admin db, then ledgersmb.conf then Environment variables
That results in sane overrides
This is an all new layer. It's currently handled by manually editing
When importing existing DB's I'd expect setup.pl to handle setting some sane values for the admin DB
Beta Was this translation helpful? Give feedback.
All reactions