https gadget in finesse

Version 1
    This document was generated from CDN thread

    Created by: Karthik Bahiradhan on 25-03-2013 06:01:52 AM
    hi, i have hosted custom https application in IIS. And created the XML for that application to integrate into Finesse 9.1. In my desktop layout i am calling this xml as https://XXX.XXX.XX.XX/Securitytest/MainTab.xm,but there was exception while rendering the gadget. exception is as follows "There were issues rendering this gadget. peer not authenticated https://XXX.XXX.XX.XX/Securitytest/MainTab.xml" also find my xml as attached

    Subject: RE: https gadget in finesse
    Replied by: David Lender on 25-03-2013 02:07:06 PM
     Finesse added support in 9.1.1 for hosting the desktop in https and optionally requiring it using using a cli command "utils finesse application_https_redirect enable"  
    See  the Finesse 9.1.1 installation and getting started guide FAQ on using the cli command "utils finesse application_https_redirect enable"  
    We have not tested a third party gadget being hosted on a remote webserver with https so we cannot support it currently.  
    The alternative is to host the custom gadget on the finesse webserver using the 3rdparty gadget sftp account described in the Cisco Finesse Web Services Developer Guide.   If you decide to use the gadget hosting, take special note of  
    CSCue46832 - reset_3rdpartygadget_password fails  
    Symptom: Any of the following CLI commands will fail to execute and will hang at a password prompt when attempted.         utils finesse application_https_redirect*       utils finesse notification*       utils reset_3rdpartygadget_password   This will lock your current console session till the system is rebooted.  
    Conditions: If you install Finesse with an administrator account and the username is not "administrator" in all lower case. 
    Workaround: Another console can be opened if you are connected directly to the system by pressing alt + any of the function keys [F1-F6] for a total of up to 6 separate console sessions.    If you are connected via ssh, simply disconnect and reconnect to gain a new session.   To prevent this from happening again when running these commands, you can create an additional CLI account that uses the username "administrator" (all lower case) with limited access to CLI commands.  This account will be able to run these commands without an additional password prompt that locks the session.   To do this, run the following command while logged into CLI the administrator account created when you originally installed the system.    set account name administrator   Select 1 for the privilege level at the prompt and press enter. Type the desired password for this new account and press enter at the prompt.   You may then logout and log back in with this "administrator" username and password.  The CLI commands should then work as expected whenever you are logged into the CLI using this account.   Note: The issue is resolved in Finesse 9.1(1) ES2 and 10.0(1) releases.