Saltar al contenido principal
Version: v19 R8

On Mobile App Authentication

On Mobile App Authentication( mobileInfo : Object ) -> result : Object

mobileInfoObject->Information passed by the mobile application
resultObject<-Authentication status


The On Mobile App Authentication 4D database method is in charge of managing mobile app authentication to 4D Server or 4D. It is automatically called by 4D when a user agent sends a login request to 4D Server or 4D for the first time.


A user agent is defined by an application ID, a device ID, and a team ID. These ids are passed to the On Mobile App Authentication database method (see below). :::

The On Mobile App Authentication database method is always called for a first connection, even if the mobile application was built in Guest mode.

The method receives all necessary information from the mobile application in the mobileInfo parameter (object), and must return an authentication status in the result parameter (object). You must declare and initialize these parameters as follows:

//On Mobile App Authentication database method
#DECLARE ($mobileInfo : Object) -> $result : Object

// ...Code for the method
$result:=New object() //do not forget to create the object to return

The following properties are received in the mobileInfo object parameter:

emailTextoUser email. Not mandatory, can be empty for guest access
applicationObjectInformation about the mobile application
idTextoMobile application id
nameTextoMobile application name
versionTextoMobile application version
deviceObjectInformation about the mobile device (usually, a mobile phone)
idTextoGenerated unique device id
versionTextoSystem version of the device
descriptionTextoDescription of the device
simulatorBooleanoTrue if the device is a simulator
teamObjectApple Developer Team information
idTextoTeam id (allows developers to use the Xcode project Build and Run functionality)
languageObjectLanguage settings of the user device
idTextoUser device current language id, ex: en_US
regionTextoUser device current region, ex: US
codeTextoUser device current language, ex: en
parametersObjectAny additional information that could be added by the mobile app for custom use
sessionObjectSession information
idTextoUUID of the Session object on the 4D server
ipTextoClient IP address


You can access the Session object automatically created on the 4D server from this database method. You can use this object to control the mobile session. If the server is restarted, the id and privileges of existing mobile sessions are automatically restored. Other session properties such as Storage, expirationDate and idleTimeout are reset.


After processing information, the database method should return a result object with the following properties:

userInfoObjectUser values to filter queries.
successBooleanoTrue if authentication is successful, False otherwise. If success=False, the connection is denied.
statusTextTexto(Optional) Message to display on the mobile application. If success=true, welcome message; if success=false, can be used to provide user with an explanation.
verifyBooleano(Optional) True if you want to validate the first login of the user session, False otherwise. Default is False

The connection is automatically rejected if:

  • no value is set to result or result is not defined,
  • an invalid value is set to result,
  • the On Mobile App Authentication database method is not defined in the application.

The connection is automatically accepted if it comes from "localhost" since it is considered a developer testing connection.

Authenticating a mobile request

Basically, authenticating a mobile application connection request is based upon the provided email. For example, if you want to grant access only to connections from emails at domain, you can write in the On Mobile App Authentication database method:

 #DECLARE ($mobileInfo : Object) -> $result : Object  

If($"@"+Char(At sign)+"")
End if

You can also identify the user agent using the,, and from the $mobileInfo object, and decide to allow or deny access.

If you want to validate emails afterwards, return True in $result.verify.

Guest access

If the mobile application has been built with the "Requires an email to connect" option unchecked, it is a "guest mode" application. Then, the $ string will be provided empty. In this case, you can:

  • allow access to guests by returning True in $result.success. If you want to validate access afterwards, return True in $result.verify.
  • identify and evaluate guest access using the user agent information, the decide to allow or deny access.
  • deny access to guests by returning False in $result.success. This can be done for example if the server is in maintenance mode. In this case, an error will be displayed on the mobile app if the user clicks on the Reload button.


Here is a template example for a On Mobile App Authentication database method:

//On Mobile App Authentication database method
#DECLARE ($mobileInfo : Object) -> $status : Object

var $Boo_simulator : Boolean
var $Txt_appID;$Txt_appName;$Txt_appVersion;$Txt_device;$Txt_deviceID;$Txt_email : Text
var $Txt_IP;$Txt_languageCode;$Txt_languageId;$Txt_languageRegion;$Txt_osVersion;$Txt_sessionId : Text
var $Txt_teamID : Text

//Get user email

If(Length($Txt_email)=0) //no email was provided
// Guest mode - allow or deny connection
// $status.success:=False if you want to deny guest access

// Optional welcome message to display on mobile App.
$status.statusText:="Welcome to my application"

// Authenticated mode - Allow or not the connection
If(Is compiled mode) // Deployment version

//Allow, for example, emails from the domain
$status.success:=($"@"+Char(At sign)+""))

Else //Development version

//Allow all adress for testing purposes

End if


//Optional welcome message to display on mobile App.
$status.statusText:="Authentication successful"


$status.statusText:=$" is not an authorized email address."

End if
End if

// Get App information if identification is needed (optional)
$Txt_appID:=$ // App Id
$Txt_appName:=$ //App Name
$Txt_appVersion:=$mobileInfo.application.version // App Version
End if

//Get Device information if identification is needed (optional)
$Txt_device:=$mobileInfo.device.description //Device Description
$Txt_deviceID:=$ //Device Id
$Txt_osVersion:=$mobileInfo.device.version //System Version
$Boo_simulator:=$mobileInfo.device.simulator //True if device is a Simulator
End if

//Get the Team information if needed (optional)
$Txt_teamID:=$ //Team Id
End if

//Get the User Language information (optional)
End if

//Get the session information
//Could be stored for future use.
$Txt_sessionId:=$ //UUID created for this authentication
$Txt_IP:=$mobileInfo.session.ip //IP address
End if

//Get the App parameters
//Any additional information that could be added by mobile app for custom use (object)
End if