Saltar para o conteúdo principal
Versão: 20

Página segurança

This page contains options related to data access and protection for your desktop applications.

Note: Para uma visão geral dos recursos de segurança de 4D, consulte o guia de segurança 4D.

Acesso aos dados / Acesso de usuários remotos​

These settings do not apply to project databases opened in single-user mode.

  • Design and Runtime Explorer Access: Gives the specified group the ability to enter the Design environment of the database and display the Runtime Explorer.

    Note que:

    • Setting an access group in the Design environment also lets you deactivate the Create table option in the data import dialog box. For more information about this dialog box, refer to Importing data from files.

    • The Designer and Administrator always have access to the Design environment and Runtime Explorer, even if they are not explicitly part of the specified access group. For more information about users and user groups, refer to the Users and groups chapter.

  • Default User: When a Default User has been set, every user that opens the database or logs onto it has the same access privileges and restrictions defined for this Default User. Já não é necessário introduzir um nome de usuário. Moreover, if you have not associated a password with the Default User, the Password dialog box no longer appears and the database opens directly. This option simplifies access to the database while maintaining a complete data control system.

    • If you have associated a password with the Default User, a dialog box appears when the database is opened and the users must enter a password.
    • If you haven't associated a password with the Default User, the User Identification dialog box will not appear.Note: You can "force" the display of the User Identification dialog box when the "Default User" mode is active, for instance in order to connect as Administrator or Designer. To do so, press the Shift key while opening the database or connecting to it.

  • Display User List in Password Dialog Box: If this option is checked, users must choose their name from the list of users and enter their password in the User Identification dialog box. Se essa opção não estiver marcada, os usuários deverão digitar o nome e a senha. Para obter mais informações sobre as duas versões da caixa de diálogo de senha, consulte a seção "Visão geral do controle de acesso" em Visão geral do controle de acesso.

    • User List in Alphabetical Order (only available if the previous option is checked): When this option is checked, the list of users in the password entry dialog box is sorted by alphabetical order.

  • Users can change their password: When this option is checked, a Change button is displayed in the User Identification dialog box. This button lets the user access a dialog box that can be used to change their password (for more information about this dialog box, refer to the "Modification of password by user" in Ensuring system maintenance). If desired, you can hide the Change button so that users cannot modify their passwords. Para o fazer, basta desmarcar esta opção.

Opções​

  • Filtering of commands and project methods in the formula editor and in the 4D View Pro and 4D Write Pro documents: For security reasons, by default 4D restricts access to the commands, functions and project methods in the Formula editor in Application mode or added to multistyle areas (using ST INSERT EXPRESSION), 4D Write Pro and 4D View Pro documents: only certain 4D functions and project methods that have been explicitly declared using the SET ALLOWED METHODS command can be used. You can completely or partially remove this filtering using the following options.

    • Enabled for all (default option): Access to commands, functions and project methods is restricted for all users, including the Designer and the Administrator.
    • Disable for the Designer and the Administrator: This option grants full access to 4D commands and to methods only for the Designer and Administrator. It can be used to set up an unlimited access mode to commands and methods while remaining in control of the operations carried out. During the development phase, this mode can be used to freely test all the formulas, reports, and so on. During operation, it can be used to set up secure solutions that allow access to commands and methods on a temporary basis. This consists in changing the user (via the CHANGE CURRENT USER command) before calling a dialog box or starting a printing process that requires full access to the commands, then returning to the original user when the specific operation is completed. Note: If full access has been enabled using the previous option, this option will have no effect.
    • Disabled for all: This option disables control within formulas. When this option is checked, users have access to all the 4D commands and plug-ins as well as all project methods (except for invisible ones). Nota: essa opção tem prioridade sobre o comando SET PERMITIDO DE METES. Quando está selecionado, este comando não faz nada.

  • Enable User Settings: You need to check this option to be able to display separated dialog boxes for user settings. When this option is checked, up to three dialog boxes are available: Structure Settings, User Settings, and User Settings for Data File. For more information, refer to User settings.

  • Execute "On Host Database Event" method of the components: The On Host Database Event database method facilitates the initialization and backup phases for 4D components. For security reasons, you must explicitly authorize the execution of this method in each host database. Para o efeito, é necessário marcar esta opção. Por padrão, não está marcada.

    Quando esta opção está seleccionada:

    Quando não é verificado:

    • 4D components are loaded but they have to manage their initialization and backup phases themselves.
    • the developer of the component has to publish the component methods that must be called by the host database during these phases (startup and shutdown)
    • the developer of the host database must call the appropriate methods of the component at the right time (must be covered in the component documentation).