Difference: AppxHTMLClient546 (9 vs. 10)

Revision 102018-06-05 - JeanNeron

 			 META TOPICPARENT 
			 name="Appx546Installation" 
		
 APPX HTML Client 5.4.6 & Higher
- META TOPICPARENT
+ name="Appx546Installation"
  Automatic Logins
-<
<
+Starting in Release 6.0, you can configure the client for Automatic logins. This is a login where the user is not presented with a login screen, but is taken directly to the startup process. You control which user credentials will be used by configuring the server connector.
->
>
+Starting in Release 6.0, you can configure the client for automatic logins. This is a login where the user is not presented with a login screen, but is taken directly to the startup process. You control which user credentials will be used by configuring the server connector.
 This is configured in the server connector for better security. Your configuration file will probably include a valid user id/password for your server, so we don't want it in the web server folder.

The settings are in the 'appx-client-automaticLogin.js' file in your server connector folder. The variables you can change are:
-<
<
+"appx-allow-noLogin" must be set to 'true'. If this is set to false, no matter what variables are provided the HTML Client will not allow Automatic logins.
->
>
+"appx-allow-noLogin" must be set to 'true'. If this is set to false, no matter what variables are provided the HTML Client will not allow automatic logins.
 "appx-allow-specific" can be set to 'true' or 'false'. If this is set to 'true', then APPX will run either the process specified below or the process specified in the URL (if 'appx-use-specific' is also set to true). If this is set to false, the process specified as the User's startup process in APPX System Admin will be run.
->
>
+The above settings CANNOT be overriden via the URL. This is by design and improves the security of the automatic login feature.

The following settings can be overridden via the URL (see keyword list below):
 "appx-use-noLogin" can be set to 'true' or 'false'. If 'true' this tells the HTML Client that all logins are automatic login. If 'false', then the login URL must include 'requireLogin=true' to request an automatic login. The 'false' setting allows you to have both automatic and normal logins.
-<
<
+"appx-use-specific" can be set to 'true' or 'false'. If "true" APPX will automatically run the process specified by the application related settings below. If 'false', the applications settings can be specified in the URL.
->
>
+"appx-use-specific" can be set to 'true' or 'false'. If "true" APPX will automatically run the process specified by the application related settings below or by the URL. If 'false', the process specified as the User's startup process in APPX System Admin will be run.
 "appx-auto-user" should contain the login user ld
-<
<
+"appx-autoc-pswd" should contain the password
->
>
+"appx-auto-pswd" should contain the password
 "appx-auto-host" should contain the APPX host
 URL String variables
-<
<
+You can specify the following variables in the URL. These will override the settings in the 'appx-client-AutomaticLogin.js' file.
->
>
+You can specify the following variables in the URL. These will override the settings in the 'appx-client-automaticLogin.js' file.
-<
<
+requireLogin ---- true/false value: true = user is required to login, false = you are using Automatic login
specific ---- true/false value: true = you are logging user into a specific process, false = you are using normal login
user ---- Login Id
password ---- Password
host ---- Server
port ---- Port
application ---- application to run
database ---- database to use
procType ---- process type you are running
process ---- process to run


Examples:
->
>
+requireLogin ---- true/false value: true = user is required to login, false = you are using automatic login
specific ---- true/false value: true = you are logging user into a specific process, false = you are using normal login
user ---- Login Id
password ---- Password
host ---- Server
port ---- Port
application ---- application to run
database ---- database to use
procType ---- process type you are running
process ---- process to run


Examples:
-<
<
+Logging in as an Automatic user, using all the settings ithe 'appx-client-AutomaticLogin.js' file:
->
>
+Logging in as an automatic user, using all the settings ithe 'appx-client-automaticLogin.js' file:
 http://<html client server>?requireLogin=false
-<
<
+Logging in as an Automatic user but overriding the startup process:
->
>
+Logging in as an automatic user but overriding the startup process:
 http://<html client server>?requireLogin=false&specific=true&application=DMO&database=DMO&procType=MENU&process=MAIN%20MENU
  If you're having trouble with Remote connections, this page has some tips
  If the client seems to hang while loading images or tables, that its a very good indicator that MongoDB server has stopped. If MongoDB server needs to be started or restarted then make sure you restart the appxConnector service after MongoDB is running.
  Your mongodb driver may be out of date. Use 'npm install mongodb' as root/Administrator to make sure you have the latest version
-<
<
+ If the Local Connector gets stuck on 'Updating' after installing a new version, try terminating the 'nw' process and deleting the AppxLocalConnector folder in the user's home directory.
->
>
+ If the Local Connector gets stuck on 'Updating' after installing a new version, try terminating the 'nw' process and deleting the AppxLocalConnector folder in the user's home directory.
  Comments

View topic | History: r16 < r15 < r14 < r13 | More topic actions...