Project

General

Profile

Edit History

Database Setup After Webserver initialization Shared » History » Version 7

Sargis Dallakyan, 09/02/2015 06:18 PM

1 1 Anchi Cheng 
h1. Additional Setup After Webserver initialization
2 





    3
    7
    Sargis Dallakyan
    
If your webserver installation is successful, a number of tables will be propagated in the databases. There were several options for setting up database user privileges recommended in [[Database Server Installation]]. The following additional steps should be taken, depending on which option you previously used.





    4
    1
    Anchi Cheng
    





    5
    3
    Amber Herold
    
* *Option 1: More secure - Restrict Drop and Delete priviledges*





    6
    
    
    
 





    7
    2
    Amber Herold
    
If you are using the more secured privilege settings we recommended in [[Database Server Installation]], you should expand the privileges of these three tables at this point:





    8
    3
    Amber Herold
    
 





    9
    1
    Anchi Cheng
    
<pre>





    10
    
    
    
GRANT DELETE ON leginondb.ViewerImageStatus TO usr_object@'localhost';





    11
    6
    Anchi Cheng
    
GRANT DELETE ON projectdb.shareexperiments TO usr_object@'localhost';





    12
    
    
    
GRANT DELETE ON projectdb.projectowners TO usr_object@'localhost';





    13
    1
    Anchi Cheng
    
GRANT DELETE ON projectdb.processingdb TO usr_object@'localhost';





    14
    
    
    
</pre>





    15
    
    
    
If you use Leginon to do robotic grid screening, you will also need to do the following to grant delete privileges to the these tables at the mysql prompt:





    16
    
    
    
<pre>





    17
    
    
    
GRANT DELETE ON projectdb.gridboxes TO usr_object@'localhost';





    18
    
    
    
GRANT DELETE ON projectdb.grids TO usr_object@'localhost';





    19
    
    
    
GRANT DELETE ON projectdb.gridlocations TO usr_object@'localhost';





    20
    
    
    
</pre>





    21
    2
    Amber Herold
    





    22
    3
    Amber Herold
    
* *Option 2: Less secure - Allow all privileges*





    23
    
    
    
&nbsp;





    24
    2
    Amber Herold
    
If you are allowing all privileges, no further steps need to be taken.





    25
    
    
    





    26
    3
    Amber Herold
    
* *Option 3: Allows access from all computers in the domain*





    27
    
    
    
&nbsp;





    28
    2
    Amber Herold
    
You may choose to assign a domain to your commands and use a wildcard to allow access from all computers in the domain.





    29
    3
    Amber Herold
    
&nbsp;





    30
    2
    Amber Herold
    
<pre>





    31
    
    
    
GRANT DELETE ON leginondb.ViewerImageStatus TO usr_object@'%.mydomain.edu';





    32
    
    
    
GRANT DELETE ON projectdb.processingdb TO usr_object@'%.mydomain.edu';





    33
    
    
    
</pre>





    34
    
    
    
Again, if you use Leginon to do robotic grid screening, you may want to grant delete privileges to the these tables at the mysql prompt:





    35
    
    
    
<pre>





    36
    
    
    
GRANT DELETE ON projectdb.gridboxes TO usr_object@'%.mydomain.edu';





    37
    
    
    
GRANT DELETE ON projectdb.grids TO usr_object@'%.mydomain.edu';





    38
    
    
    
GRANT DELETE ON projectdb.gridlocations TO usr_object@'%.mydomain.edu';





    39
    
    
    
</pre>