4D v14.3
Web/REST page
- 4D Design Reference
-
- Database settings
-
- Overview
- Using user settings
- General page
- Interface page
- Compiler page
- Database/Data storage page
- Database/Memory page
- Moving page
- Backup/Scheduler page
- Backup/Configuration page
- Backup/Backup & Restore page
- Client-server/Network options page
- Client-server/IP configuration page
- Web/Configuration page
- Web/Options (I) page
- Web/Options (II) page
- Web/Log (type) page
- Web/Log (backup) page
- Web/Web Services page
- Web/REST page
- SQL page
- PHP page
- Security page
- Compatibility page
Web/REST page
This page contains the options used to enable and control 4D Mobile access (via REST) for the 4D database.
4D Mobile access allows Wakanda applications to access the data of your database directly. For more information, refer to the 4D Mobile manual.
For security reasons, by default, 4D does not respond to 4D Mobile requests (via REST). If you want to use this functionality, you must check the Activate 4D Mobile service option in order for requests from Wakanda to be processed and so that the Wakanda / 4D connector can be implemented.
Note: 4D Mobile services use the 4D HTTP server, so you need to make sure that the 4D Web server or 4D Server is started.
The warning message "Caution, check the access privileges" is displayed when you check this option to draw your attention to the fact that when 4D Mobile services are activated, by default access to database objects is free as long as the 4D Mobile accesses have not been configured.
This option specifies the group of 4D users that is authorized to establish the link to the 4D server from the Wakanda application.
By default, the menu displays <Anyone>, which means that 4D Mobile accesses are open to all users.
Once you have specified a group, only a 4D user account that belongs to this group may be used to access 4D by means of a 4D Mobile request -- in particular, to open a session on the 4D Server using the mergeOutsideCatalog() method. If an account is used that does not belong to this group, 4D returns an authentication error to the sender of the request.
Note that in order for this setting to take effect:
- the 4D password system must be activated (a password must have been assigned to the Designer, see Activating access control),
- the On 4D Mobile Authentication database method command must not be defined. If it exists, 4D does not take into account any access settings defined in the Database Settings.
Product: 4D
Theme: Database settings
4D Design Reference ( 4D v14.3)
Inherited from : Web/REST page ( 4D v14 R2)
