Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Postgres account #2

Closed
dark668 opened this issue Nov 2, 2016 · 3 comments
Closed

Postgres account #2

dark668 opened this issue Nov 2, 2016 · 3 comments
Assignees
@woanware

Comments

@dark668
Copy link

dark668 commented Nov 2, 2016

is there any method to permit another specific user being configured other than postgres, I haven't tried yet but not sure if this will have an impact on the client service?
@woanware
Copy link
Contributor

woanware commented Nov 2, 2016

As long as you change the permissions on all of the DB objects then you can use another user e.g. an application specific one

@dark668 dark668 closed this as completed Nov 2, 2016
@woanware
Copy link
Contributor

woanware commented Nov 2, 2016 •
edited
Loading

I will add a script in the future that will allow the user to create a new DB user and set the correct permissions on each of the objects/tables

@woanware woanware reopened this Nov 2, 2016
@woanware woanware self-assigned this Nov 2, 2016
@woanware
Copy link
Contributor

The v1.0.2 release now includes a script to define the user/password/privs. The installation instructions have also been updated to explain the changes:

https://github.com/infoassure/autorun-logger-server/blob/master/documents/installation.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@woanware woanware

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@woanware @dark668