To increase developer’s efficency with m-Power, mrc has unveiled a new sign-on configuration option: The ability to automatically inherit their m-Power interface authentication into their run-time applications!
Until now, developers were forced to log-in to their applications after every recompile. By installing the configuration below, this will no longer occur.
By adding a few configuration options to the mrcSignon2.xml file, m-Power makes it possible to quickly and easily integrate your m-Power interface log-in directly into your run-time apps. Specifically, this configuration can be used to share the session and username between the m-Power interface and generated applications in a development environment. Customers will find this useful in that it should eliminate the need to constantly sign back in to development applications every time Tomcat reloads. While Tomcat will still reload from time to time, the new logic will automatically log the user back into the generated applications as long as they are still signed into the m-Power interface.
To enable this feature, it requires the configuration of the mrcSignon2.xml file and also the addition of one property to the web.xml file inside of mrcwebgui.
1) Copy mrcSignon2.xml from: m-power\mrcjava\mrcclasses
To: m-power\mrcjava\WEB-INF\classes\NAME OF YOUR DATA DICTIONARY
Copy mrcSignon2.html from: m-power\mrcjava\mrcclasses
To: m-power\mrcjava\WEB-INF\classes\NAME OF YOUR DATA DICTIONARY
2) Open the mrcSigon2.xml file in a text editor and change the validationType property to “9”
3) Add the following properties inside the “group” tag in mrcSignon2.xml:
<sso_url value="mpower"/>
<ssoCookieName value="MPSESSIONID"/>
<ssoUser value="mrcuser" />
<ssoPassword value="mrcuser" />
<ssoType pdesc="ssoType" value="1" />
4) Open the mrcwebgui/WEB-INF/web.xml file in a text editor and add the following configuration inside the “web-app” tag:
<servlet>
<servlet-name>security_servlet</servlet-name>
<servlet-class>com.mrc.session.CheckMpowerLogin</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>security_servlet</servlet-name>
<url-pattern>/securitycheck</url-pattern>
</servlet-mapping>
5) Restart tomcat.
*NOTE: When you need to promote your mrcSignon2.xml page to production, make sure to change the validationType property to a value other than “9”. You need to do this because validationType “9” only works when the m-Power development interface is present, which it does not in Production.
Editor’s Note: If you are interested in configuring Single Sign On (SSO) for your m-Power applications with a 3rd party tool, our consultants are standing by to assist.