3 Replies Latest reply on Aug 7, 2013 8:07 AM by djohnstone@informatica.com

    UMDS Authentication

    New Member

      Hi,

       

      I am attemption to configure authentication of the UMDS component.

       

      When setting application authentication I get LoginDenied & the msg:

       

      "Received Status 1 from server - authentication 'none' not enabled"

       

      I have set the appl_name in the clients UMDSServerConnection constructor. Is there another property or option I am missing?

       

      umds-cfg.xml has:

      :

           <authentication>

               <basic xml:space="preserve">/home/asgdev/mSeries/blizzard/blizzard-server/current/properties/umds-auth-cfg.xml</basic>

          </authentication>

       

      umds-auth-cfg.xml has :

       

          <application name="myAppName">

              <client>

                  <!-- Allow application "myAppName" to reconnect and give ability to override this setting -->

                  <server-reconnect client-write="yes">0</server-reconnect>

              </client>

              <!-- Allow application "myAppName" to send messages regardless of who is using it -->

              <permissions> <can-send>1</can-send> </permissions>

          </application>

       

       

      Also, is it possible to have authentication on the web-monitor?

       

      Kind Regards,

      Stephen Smith

        • 1. UMDS Authentication
          New Member

          Any thoughts on this would be greatly appreciated.

           

          Stephen

          • 2. UMDS Authentication
            New Member

            I've created service request 1-221227377 to respond to this, and contacted Jamil Ahmed to get you added to an appropriate support project. You should have received an email about this. If not, contact me again and I'll make sure it's sorted.

            • 3. UMDS Authentication
              New Member

              Hi,

               

              Thanks for your questions and I hope that my answers on your service request were sufficient. I wanted to send an update for anybody else who has been following this discussion.

               

              In the latest version of UMDS, 1.1.1.3, there is an issue with the Application authentication logic - this will be resolved in a future release. Until then, the workaround is to use User authentication to control access to the UMDS server. 

               

              There is also an enhancement request to allow the user to enable or disable the various control objects within the UMDS webmonitor, specifically whether the webmonitor will include the options to disconnect a client or stop the server entirely.

               

              Kind regards

               

              --

               

              David Johnstone

              Senior Technical Support Engineer

              Global Customer Support