User Identity on Remote Instance
A user’s identity when working on a remote instance depends upon the type of access authorized.
• When access to a remote instance is authorized using an Installation Password, users retain their local identities (User IDs) when working on the remote instance.
• When access is authorized through a user name and password (whether an operating system account or DBMS authentication) on the remote instance’s host machine, users take on the identity of this account when working on the remote instance.
In either case, the user’s privileges and permissions on the remote instance can differ from those on the local instance. For example, a user can have system administrator privileges on the local instance but only very general, low-level privileges and permissions on the remote instance. It is important to make sure that the privileges and permissions assigned to you on the remote instance are adequate for the work that you intend to perform.
User privileges and permissions are set up individually for each instance using Visual DBA or CREATE USER statement. They apply only to the instance on which they are set up. For more information about this procedure, see the Security Guide.
Note: Using Network Utility or Visual DBA, you can access a list of users on Ingres server nodes and establish a connection at the user level under a different user name. For more information, see Impersonating Another User in online help for either of these visual tools.
Last modified date: 08/28/2024