Table of Contents
This document is intended for database administrators, system administrators, and application developers. To use this document, you need to know the following:
Relational database concepts in general
Basic administration knowledge of the underlying operating system
Please use the bayeos system account to access your local bayeos database instance for administration purposes.
There is no need to change any setting in
A typical session looks like the following:
ssh -l root <hostname> su bayeos psql -d bayeos select set_user('root'); ...
This is probably the main task in every administrators job. Therefore the following paragraph describes how to manage this.
BayEOS has build in capabilities for database, LDAP and IP authentication. The methods are configurated by entries in database tables. Please configure the authenticaton method before creating new users. The following subsections describe the authentication methods in more detail.
This is the classic authentication approach using passwords stored in a database table named auth_db. A record for local authentication named as 'LOCAL' is provided by default. You can add additional records to this table to authenticate users against a different database or schema. Please be aware to provide the appropriate JDBC library to your application server.
Attributes in table bayeos.auth_db
Alias to access this record
JDBC database connection definition, e.g.:"jdbc:postgresql://localhost:5432/bayeos"
Username for JDBC connection
Password for JDBC connection
Select statement to access user password using crypt function, e.g: "select crypt(?,substr(pw,1,2)) = pw from benutzer where login like ? and locked = false;"
Update statement to update user password in database e.g.: "update benutzer set pw = crypt(?,gen_salt('des')) where login like ?;"
This type of authentication method is quite useful if your company is hosting a central LDAP repository. To use this method just add an entry providing the necessary information before creating new users.
Attributes in table bayeos.auth_ldap
Alias to access this record
LDAP server hostname
Distinguished name to start the search. The username must be provided as an input parameter, e.g. "uid=:?,ou=people,dc=uni-bayreuth,dc=de"
Flag to specify whether LDAPS is used or not. For LDAPS a key store is necessary. You must import the certificate of your LDAP Server into the default store of the server JRE. The default keystore for your JRE can be found in /usr/lib/jvm/jre/lib/security. The key can be imported by the keytool utility:
keytool -import -alias myAlias -file myCertificate.crt -keystore cacerts -storepass changeitPlease restart the Tomcat Server after the import.
Port for ldap connection. Use 389 for default ldap or 636 for ldaps connections.
Authentication for a specific user is controlled by his ip address. A specific IP filter can be used to assign users to access methods.
Attributes in table bayeos.auth_ip
Some valid examples entries in table auth_ip are shown in the following figure. When user 'import' is trying to login from 22.214.171.124 no password is needed.
network | login | access -----------------+--------+---------- 126.96.36.199 | import | TRUST 188.8.131.52/8 | * | PASSWORD 184.108.40.206/24 | * | PASSWORD
You can add users to the database by calling the create_user function:
login: user name
password: user password, can be blank for LDAP authentication
name: user name
auth_name: authentication name
A typical administrator session to create a new local database user 'bill' for Bill Gates will look like:
su bayeos psql -d bayeos select set_user('root'); select create_user('bill','PASSWORD','Bill Gates','DB','LOCAL');
Users can be dropped by the
function passing in the user name. A typical administrator session
to drop a user 'bill' will look like:
su bayeos psql -d bayeos select set_user('root'); select drop_user('bill');
To set the password for a local database user just call the
BayEOS right system is based on the well known UNIX right system. Rights are bound to a specific object and can be granted to users or roles. The following rights are available:
Read: Right to read objects like series or locations
Write: Right to create and update objects
Execute: Gives full access in combination with the read and write right (rwx). Users with full access are allowed to delete objects and to add/delete references on objects
Inherit Flag: Forwards rights to all child objects
Commands to manage rights:
Roles are a mechanism to grant rights to several users. The following functions are available to manage roles:
grant_role(username text, role_alias text)
revoke_role(username text, role_alias text)
The default role for all new users is called 'All Users'. The role has read access to all root nodes like folders or units.
Each observation series has a time zone property. The default timezone of BayEOS is GMT+1.
One main functionality of BayEOS is its capability to calculate aggregation values on base of orginal measurements. To speed up the calculation time we use a hierachy approach. Each coarser interval uses the calculation values of it's successor. Aggregation functions and intervals can be configurated in system tables aggr_intervall and aggr_funktion.
Attributes in table bayeos.aggr_intervall
Attributes in table bayeos.aggr_funktion
[@] quantity unit [quantity unit...] [direction]
The following housekeeping functions can be used to manage aggregates: