Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Matt McDawell: "Your practical knowledge & experience, supported by your dedication and hard work set new standards. Taking you into account is the best decision our company has made".
Dan Flazer: "Your new product and your assistance with us was excellent...will prove invaluable to the future of our company".

More

Add your opinion

MaxDB Maestro online Help

Prev Return to chapter overview Next

Editing role properties

Role Editor provides you with an ability to edit role properties. The Properties tab allows you to change the role password, to manage role content (members of the current role, role the current role is member of, role variables), and other role attributes. The detailed description is given below.
 

 

Members

You can edit here a list of roles which are members of the new role. (This in effect makes the new role a "group".) Admin option gives to the role the right to grant membership in this role to others. If Grant option is specified, the current role may in turn grant it to others. Without a grant option, the recipient cannot do that. Grant options cannot be granted to PUBLIC.

 

Members of

Use the tab to edit a list of roles to which the role is added as a member.

 

Variables

The tab is implemented to view and edit this role's session defaults for the specified configuration parameters to the given value.

 

Name

Edit the role name within the field. To do it more quickly use the Rename Role link of pop-up menu in the explorer tree.

 

Can Login

The checkbox determines whether a role is allowed to log in; that is, whether the role can be given as the initial session authorization name during client connection. A role having with the option checked can be thought of as a user. Roles without this attribute are useful for managing database privileges, but are not users in the usual sense of the word.

 

Inherits rights from parent roles

The clause determines whether a role "inherits" the privileges of roles it is a member of. A role with the option checked can automatically use whatever database privileges have been granted to all roles it is directly or indirectly a member of. Otherwise, membership in another role only grants the ability to set role to that other role; the privileges of the other role are only available after having done so.

 

Connection limit (-1 for no limit)

The field value specifies how many concurrent connections the role can make. -1 (the default) means no limit.

 

Valid until

The field contains an absolute time after which the role's password is no longer valid. If this clause is omitted the password will be valid for all time.

 

Can Create Users (Superuser)

This clause determines whether the new role is a "superuser", who can override all access restrictions within the database.

 

Can create databases

The option defines a user's ability to create databases. If it is specified, the role being defined will be allowed to create his own databases. Set false to deny the role the ability to create databases.

 

Can create roles

Use the checkbox to define a role's ability to create databases. If the option is specified, the role being defined will be allowed to create new databases. Specifying the opposite will deny a role the ability to create databases.

 

Can update system catalog directly

Use System ID to specify the PostgreSQL role ID of the new role. This is normally not necessary, but may be useful if you need to recreate the owner of an orphaned object. If this is not specified, the highest assigned role ID plus one (with a minimum of 100) will be used as default.

 

Password

Use the field to edit the role's password. If you do not plan to use password authentication you can omit this option, but then the role will not be able to connect if you decide to switch to password authentication.

 

Password Encrypted

This Checkbox allows you to control whether the password is stored encrypted in the system catalogs.



Prev Return to chapter overview Next