OpenEdge Development: Mobile Applications - Product ...

login( ) method
login( ) method
Starts a user login session on the current Session object by sending an HTTP request
with user credentials to a URI for a specified Mobile Web application. If the user
credentials are authenticated, the login session is started with a unique session ID for
that session that is also passed to the AppServer that implements the Mobile Web
application. If the Mobile Web application is so configured, along with the session ID, it
also sends a single sign-on (SSO) client-principal with the user credentials to the
AppServer. The method also returns a code indicating the success of the login request.
Notes: Before invoking this method, ensure that you set the authenticationModel
property on the Session object correctly (see the notes on authentication
models).
If the browser or mobile device has already authenticated a user login session,
this method completes successfully.
This method does not support proxy servers (servers that function as a security
service) in Release 11.2.
Return type: Number
Applies to: progress.data.Session class
Syntax
login ( service-uri [ , username , password [ , login-target ] ] )
service-uri
A string expression containing the URI of the Mobile Web application for which to
start the user login session. This Mobile Web application must support one or
more OpenEdge Mobile services in order to create JSDOs for the service
resources provided by the application. If HTTP Basic Authentication is in effect for
the Mobile Web application (see the notes on authentication models), this URI is
appended with a string that identifies a protected resource against which to
authenticate the login session (see login-target).
If the Mobile App from which you are logging in is a Mobile Web App deployed to
the same Apache Tomcat server as the Mobile Web application, you can specify
service-uri as a relative URI, for example, /SportsMobileApp, which is relative
to the deployment end point (Tomcat server domain or host and port).
If the Mobile App from which you are logging in is a Mobile Native App that will be
installed to run directly in a native device container, or if it is a Mobile Web App
deployed to a different Web server from the Mobile Web application, you must
specify service-uri as an absolute URI to the Tomcat server domain or host and
port, for example, http://www.progress.com/SportsMobileApp, or perhaps for
testing, http://testmach:8980/SportsMobileApp.
Note: For any Mobile App that must specify service-uri as an absolute URI,
you must maintain separate JavaScript sources to deploy the Mobile App
for different Mobile Web application environments, such as one for testing
and one for production.
OpenEdge ® Development: Mobile Applications 227