Security

System and application security and access rights management  
All user interface components, whether the case is fields, calculation results, “Parameter Collections” to, for instance, queries or database connection parameters, can be admission restricted with only the necessary rights to view and change and delete. Users, as individuals or divided into groups, can be assigned relevant situation specific rights – these determined by parameters and by fixed properties.

• Login and Authentication
  In connection with login the username and password are validated by the DM Server’s Authentication Service. From the client the DM Server receives an encrypted string, which is subsequently validated and returned in encrypted form to the client. In case that username and password validation returns “OK”, the “Database Schema Owner” (Database User) and his/her password are also returned including all the necessary connection parameters. The only location where the database user’s password is saved (in encrypted form) is, in this way, on the computer running the DM Server. As a result, this password cannot be distributed to any other DM user apart from the Database Administrator.
• Secure Database Connection Establishment (protection of database password)
  Following DM Server “Authentication Service” validation is temporarily created a local ODBC data source based on the delivered connection parameters. The very database ODBC driver is, however, embedded in the program and is not required to install this separately. The data source does not specify username and password due to the fact that these are tied in the dynamic “ConnectString” at the point in time where the transaction object establishes a connection to the database server. Data source name is also specified by the DM Server and is as such unique and the same across all clients. Other programs, such as “Sybase InfoMaker”, can also with great advantage employ this centrally configured data source, which is available when the DM client has been logged on.
• Automatic Login (Single Sign On)
   By specifying a relationship between the Dialog Manager client and a Windows domain user, the client can be automatically validated. In addition, the client that matches the current Windows domain user is automatically logged in. As a result, it is possible to completely avoid that the client is obligated to know their password. The local property is assigned to the Windows Installer package (MSI) and is in this way, like the tie between client and Windows domain user, administered centrally.
• Data Protection
  Access to- as well as the degree of use of Business Entities (collections of fields and tables) and Business Components (Dialog Manager objects, buttons, etc.) can be managed in the system. In addition, the system allows for specification of read and write rights for individual client interface components.