MX Release 3.2 (H06.25+, J06.14+)

Figure 2 Connection Data Flow

Connection Mapping

MXCS maps the client data source name in an incoming connection request to the server data

source name (names are case sensitive). If the name matches but the server data source is not

started, the connection request is rejected. If the server data source name does not exist, the

association server routes the connection to the default data source. If the default data source is not

started, the connection request is rejected.

After a data source name is assigned, the association server uses any MXCS server that was

previously used by the same user ID. If no such server is found, the association server assigns the

first available server to the connection and reinitializes the user context to the one defined in the

configuration for the data source name on the MXCS SQL server.

Security

Access authorization

Authorization for access to NonStop SQL databases uses authenticated Guardian user names. The

MXCS SQL server program (MXOSRVR) follows SQL/MX rules for accessing SQL/MX objects (and

SQL/MP rules for SQL/MP objects), and as such the SQL objects are subject to the normal SQL

rules that govern access to those objects. For example, to read from an MX table, the user must

have SELECT privilege.

Each MXCS SQL process runs under a Guardian user name that is used to authorize access to

SQL objects.

For more information about SQL/MX privileges, see the SQL/MX Reference Manual.

User Authentication

MXCS uses a connection model in which users request a connection to a named service, known

as the data source. To complete the connection, the user provides a user name and a password,

which are passed in a secure, private packet to the MXCS server.

Two formats for the username are valid:

Security 15