Security

Overview For some users, the need to implement sign-on security in front of their applications is relatively low. However, at...

Row Level Security is a highly flexible technique for controlling which records are returned based on the current user. The...

After you have implemented Sign on Security (see here), you may want to control who can see which records. For...

Overview Many developers utilize m-Power’s built-in Dictionary Security, which requires end-users to sign on before running any applications in the...

m-Power developers have the ability to log end-user activity for signon/signoff of generated applications. This functionality is quite useful for...

Occasionally, developers need their users to authenticate to the m-Power server (For row level or menu security) but do not...

As you may know, m-Power applications can be configured to require Sign-on validation so that your user must first authenticate...

How can we change the default username/password Tomcat ships with? Various areas of Tomcat are secured to prevent unauthorized access,...

Overview The menu system in m-Power offers a centralized location for end-users to access their applications (menu options). Using the...

Overview This document is applicable for m-Power clients who connect to different databases for their development and production applications. In...