OpenEdge Development: Mobile Applications - Product ...

Managing user login sessions
• The type of Mobile App you are writing and where it will be deployed: a
Mobile Web App deployed to a Web server or a Mobile Native App deployed
to an app store:
In order to log into a Mobile Web application and load any of its JSDO catalogs,
you need to provide appropriate URIs for both. If you are writing a Mobile Web
App, and it will be deployed to the same Apache Tomcat Web server as the Mobile
Web application it is accessing, all of these URIs can be relative to the Web server
root (domain or host and port). The Web browser automatically prepends these
relative URIs to the Web server root from which the Mobile Web App is loaded.
However, if a Mobile Web App is deployed to a different Web server from the one
where the Mobile Web application is deployed, all of these URIs must be absolute
and include the Web server root for the Mobile Web application.
If you are writing a Mobile Native App, all of the URIs for the Mobile Web
application and its JSDO catalogs must also be provided as absolute URIs,
because a Mobile Native App is loaded and executed from the local storage of the
mobile device, which knows nothing of the Mobile Web application its Mobile Web
App is going to access.
Note: In general, if a Mobile App requires absolute URIs, you need to maintain
separate JavaScript sources for versions of the Mobile App that you deploy
for different Mobile Web application environments, such as one for testing
and another for production.
Depending on the Web server authentication model, you might need to set up Web
resources differently to help with the Mobile App login sequence. OpenEdge provides
some default Web resources with every deployed Mobile Web application that you can
use for this purpose, or you define similar Web resources of your own.
Default Web pages to support Mobile App login
When you deploy Mobile services to a Tomcat Web server as a Mobile Web
application, OpenEdge provides default Web pages that you can use to configure
Mobile Web application authentication. The URIs for the following Web pages
(provided relative to the Mobile Web application root) support the startup and user login
of a Mobile App in a way that authenticates the user prior to requesting access to
Mobile resources, depending on the Web server authentication model:
• /index.html — Default public welcome page for Mobile App startup. This page
can be protected or unprotected depending on how you design authentication for
your Mobile App.
• /static/auth/login.html — Default Mobile Web application login page to
support HTTP Forms Authentication. With a login page configured (such as this
default), the Mobile Web application can then provide a protected Web resource
for access by the user. This might be a link on the public welcome page to a
protected Web page that the user must access to use Mobile resources, or it
might be the welcome page, itself, that is protected and requires authentication for
access by the user.
OpenEdge ® Development: Mobile Applications 119