OpenEdge Development: Mobile Applications - Product ...

OpenEdge Mobile supports the following authentication models:
• Anonymous — No authentication is required. This is the default value.
login( ) method
• HTTP Basic Authentication — The Mobile Web application requires a valid user
ID and password, but does not provide a page containing a login form (credentials
are typically entered in a generic login dialog provided by either the Mobile App,
the browser, or the native device container in which the App is running).
• HTTP Forms Authentication — The Mobile Web application requires a valid user
ID and password and provides a page containing a login form.
For more information on these authentication models and how to configure them for a
Mobile Web application, see the sections on Web server authentication models in
Chapter 5, “Deploying Mobile Applications.” For more information on the interaction
between this method and the Web server, see the sections on managing login session
in Chapter 4, “Creating Mobile Apps using JSDOs.”
Caution: You must be sure that security is configured to complete authentication
before the application requests resources in the JSDO catalog. Although it is
possible to configure application security so that the only the Mobile
resources in the catalog require authentication, Progress Software does not
recommend this approach. Instead, Progress Software recommends that
you require authentication for application resources in addition to those
defined in the catalog, and require that the authentication occur prior to
accessing any resources in the catalog. (Note: This is the purpose of the
login-target parameter, either one you pass to the login( ) method or its
default.) Once the user is authenticated, the Web server provides access to
all other resources, including catalog resources, according to the user's
authorization settings.
Note: Unless the application design guarantees that the user will be prompted by the
Web browser or native device container to provide credentials before a
login( ) call occurs, Progress Software recommends (in some cases
requires) that the Mobile App pass the credentials as parameters to the
login( ) method. In addition, you must correctly set the value of the Session
object’s authenticationModel property. Coding the Mobile App in this way
ensures that the proper credentials are submitted to the server and promotes
a favorable user experience.
See also: addCatalog( ) method, loginHttpStatus property, loginResult property,
loginTarget property, logout( ) method, serviceURI property,
userName property, authenticationModel property
OpenEdge ® Development: Mobile Applications 229