|
META TOPICPARENT |
name="Appx550Installation" |
APPX HTML Client 5.5.0/5.5.1 |
|
-
-
const cryptoEnabled = false; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
Here are a few common scenarios and their values. |
|
-
-
const cryptoEnabled = false; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
I want no reverse proxy, AES encryption ( Don't want hassle of reverse proxy configuration. I want encryption, but don't want the hassle of SSL certificates ) |
|
-
-
const cryptoEnabled = true; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
I want no reverse proxy, SSL encryption ( Don't want hassle of reverse proxy configuration, but want the best encryption ) |
|
-
-
const cryptoEnabled = false; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
I want a reverse proxy, no encryption al all. ( I want a Reverse Proxy because a reverse proxy often allows for a simpler firewall ruleset. Unfortunately, a reverse proxy requires configuration in your web server - Apache, Nginx, IIS. Keepin it simple regarding encryption. ) |
|
-
-
const cryptoEnabled = false; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
I want reverse proxy, AES encryption( I want a Reverse Proxy because a reverse proxy often allows for a simpler firewall ruleset. Unfortunately, a reverse proxy requires configuration in your web server - Apache, Nginx, IIS. I want encryption, but don't want SSL certificate hassle ) |
|
-
-
const cryptoEnabled = true; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
I want reverse proxy, SSL encryption ( I want a Reverse Proxy because a reverse proxy often allows for a simpler firewall ruleset. Unfortunately, a reverse proxy requires configuration in your web server - Apache, Nginx, IIS. I also want the best encryption possible ) |
|
-
-
const cryptoEnabled = false; // Are we using Crypto to encrypt traffic? Must be off if SSL is on
-
const useoldsocket = true; // If set to true, the non SSL capable APPX engine socket and logic are used
-
const appxLocalConnectorCert = null; // If local connector needs certificate authority point to it here
|
|
< < | |
> > | |
|
Parameters I didn't really dive into, but are worth mentioning. appxLocalConnectorCert is used if you have your own organizational certificate authority. useoldsocket is used if you enabled mandatory SSL logins with your appxLoginMgr and your appxLoginMgr is <5.5.0. If you are in a 5.5.0 environment, useoldsocket should probably be set to false. |