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.

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

Table permissions not set AssetTracker v3.2 #64

Open
bmt-johnboers opened this issue Nov 8, 2013 · 3 comments
Open

Table permissions not set AssetTracker v3.2 #64

bmt-johnboers opened this issue Nov 8, 2013 · 3 comments

Comments

@bmt-johnboers
Copy link

I noticed that for the following AssetTracker no permissions are set for the database user used by RT 4.2.0. I am using Postgres 9.1

at_scripactions
at_scriptconditions
at_scrips
at_templates

Is this related to issue #63 during which data insert fails?

@bmt-johnboers
Copy link
Author

Fixed problem by adding missing tables and sequence counters to etc/acl.Pg:

sub acl {
my $dbh = shift;

my @acls;

my @tables = qw (

at_types
at_types_id_seq
at_assets
at_assets_id_seq
at_ips
at_ips_id_seq
at_ports
at_ports_id_seq
at_scripactions
at_scripactions_id_seq
at_scripconditions
at_scripconditions_id_seq
at_scrips
at_scrips_id_seq
at_templates
at_templates_id_seq
);

foreach my $table (@tables) {
    push @acls,
      "GRANT SELECT, INSERT, UPDATE, DELETE ON $table to "
      . $RT::DatabaseUser . ";";

}
return (@acls);

}
1;

@bmt-johnboers
Copy link
Author

Pressed wrong button, reopening it

@bmt-johnboers bmt-johnboers reopened this Nov 10, 2013
@ghost
Copy link

ghost commented Jun 30, 2014

are you successfully using AT with RT 4.2.0+ ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant