hazaar/hazaar-dbi
1
0
Fork 0
Code Issues Pull requests Projects Releases 8 Packages Wiki Activity Actions

DBI Schema Manager: Allow alternative credentials #88

New issue
Closed
opened 2022-10-27 01:46:33 +00:00 by jamie · 3 comments
jamie commented 2022-10-27 01:46:33 +00:00 (Migrated from git.hazaar.io)
Copy link

The auth credentials for accessing the database are the same credentials used for schema management. I think it would be a good idea to allow these to be separate so that the schema manager user can be used to create tables, but the normal user account no longer needs this access. This can increase security, however I feel that I will then also need to include user/access/ownership functions to the schema snapshot/migration.

The auth credentials for accessing the database are the same credentials used for schema management. I think it would be a good idea to allow these to be separate so that the schema manager user can be used to create tables, but the normal user account no longer needs this access. This can increase security, however I feel that I will then also need to include user/access/ownership functions to the schema snapshot/migration.
jamie commented 2022-10-27 01:46:33 +00:00 (Migrated from git.hazaar.io)
Copy link

assigned to @jamie

assigned to @jamie
jamie commented 2022-10-27 04:13:04 +00:00 (Migrated from git.hazaar.io)
Copy link

created branch 88-dbi-schema-manager-allow-alternative-credentials to address this issue

created branch [`88-dbi-schema-manager-allow-alternative-credentials`](/hazaar/hazaar-dbi/-/compare/master...88-dbi-schema-manager-allow-alternative-credentials) to address this issue
jamie commented 2022-10-27 04:13:09 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in merge request !56

mentioned in merge request !56
jamie (Migrated from git.hazaar.io) closed this issue 2022-10-27 06:59:50 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
1.4-develop
1.3-develop
release-2.3.1
release-2.3.0
release-2.2.5
release-2.2.4
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.0
release-2.0.3
release-2.0.2
release-2.0.1
release-1.4.1
release-1.3.2
release-2.0.0
release-1.4.0
release-1.3.1
release-1.3.0
release-1.2.11
release-1.2.10
release-1.2.9
release-1.2.8
release-1.2.7
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.8
release-1.0.7
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-dbi#88
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?