We use obfuscation and 128-bit encryption. Appeon customers include
Fortune 500 companies, government, and even military. There has never
been a breach and it is a proven secure solution with more than 10
year track record.
First of all keep in mind that the whole web application's security
is not only relying on Appeon. Appeon's security is a secondary
security. The web application it is originally a PowerBuilder
application and the client/server developer should take the security
issue into consideration during the programming. Appeon did a lot of
work to secure the data transfer on the Web, and the customer use
Appeon together with other security guard mechanism to ensure the data
safe on the Web. Below is a general intr...
The default username is admin and the default password is admin. The
username and password settings for AEM can be modified in Security
settings in AEM. Refer to Security in the Appeon Server Configuration
Guide for more information.
Appeon provides built-in security mechanism to secure the web access.
Note that Appeon's security is a second layer of security since
originally it is a PowerBuilder application and the PB app developer
should take the security issue into consideration during the
programming.
Appeon will convert that security to the web, and will add on top of
that its own layer to secure the data transfer on the Web.
If you have strong concerns about the security, you can also implement
HTTPS, which is supported by A...
All your existing userID, password validation, and roles/rights
assignments you coded in PowerBuilder will be carried over to the
clients (both Windows client and mobile device).
In addition, we provide hooks to LDAP if you want to centralize
things across multiple apps.
For more complex requirements, you can use Visual Guard
(www.visual-guard.com):
* Single Sign-on (SSO),
* Identity Federation,
* Multi-tenant applications,
* SaaS Application Security
* Supporting multiple type of users...
Please revise the aem-config.xml file in the "...\inetpub\wwwroot
\appeon\AEM\config\" folder: replacing the 7th line in the file with
the line , then restarting the Appeon Server to make the changes take
effect.
Once you reset you can login into AEM with with username 'admin' and
password 'admin'.
The path for EAServer is:
"...\Sybase\EAServer\appeon\repository\%instancename%\config\" folder:
replacing the 7th line in the file with the line
You can find the above solution in Appeon Help | Trou...
It's not a simple configuration to declare the list of Mobile devises
allowed to connect to the mobile application in AEM.
However, as part of the customer username/password authentication
that they have coded in their PB application, they can add an
additional check to make sure that the mobile devise is an authorized
one. Appeon provides a PB function the customer can call to retrieve
the mobile device ID. The function is:
eon_mobile_deviceex.of_getdeviceid()
Appeon is not a Web server. It runs...
Please find attached a document about the security in Appeon Mobile