![]() To establish a trusted connection between the web application and CyberArk Identity, you need to have the same signing certificate in both the application and the application settings in the Identity Administration portal. You can either download one from the Identity Administration portal or use your organization’s trusted certificate. For details, see Send SAML Metadata to LogMeIn Rescue for SSO configuration LogMeIn Rescue requirements for SSOīefore you configure the LogMeIn Rescue web application for SSO, you need the following:Īn active LogMeIn Rescue account with administrator rights for your organization. You will need to copy some settings from Application Settings in the Identity Administration portal send them to LogMeIn Rescue. For details, see Configure LogMeIn Rescue in the Identity Administration portal. Once the application settings are configured, complete the user account mapping and assign the application to one or more roles. In the Identity Administration portal, add the application and configure application settings. Prepare LogMeIn Rescue for single sign-on (see LogMeIn Rescue requirements for SSO). ‘Name for custom field 3’: Ticket Requester phone numbersĮ.SP-initiated SSO for LogMeIn Rescue is automatically enabled when the SAML feature is activated. ‘Name for custom field 1’: Ticket SubjectĬ. ‘Name of the field’: Ticket Requester Nameī. In LogMeIn “Global Settings’ customs fields are mapped to Freshdesk ticket details as:Ī. The trackpad seems to be not working with my MacBookĠ5:31 PM John Doe: I will transfer this session to my technician and will have a look at your issue.Ġ5:31 PM The technician ended the session.ġ8. How may I help you?Ġ5:30 PM Stacy: Hi John. When the technician ends the support session, a private note will be added to a ticket.ĬHATLOG:05:30 PM Connecting to: (95.172.70.144:443)Ġ5:30 PM Connected to Applet (RSA 2048 bits, AES256-GCM- SHA384 256 bits)Ġ5:30 PM Customer Applet is running as a Windows system service.Ġ5:30 PM John Doe: hello, this is John from Support. When the session status turns to “Waiting” in the LogMeIn Rescue’s desktop console, double click the session to connect to the waiting customer. Open your Desktop LogMeIn Rescue console.ġ6. Click on ‘Send’ to send session instructions to the customer.ġ5. Remote session instructions will be copied to the ticket ‘Reply’ widget.ġ4. To take advantage of the integration, a Freshdesk agent clicks on ‘Generate New Session’ to generate a new PIN code.ġ3. The LogMeIn Rescue widget appears in the ticket sidebar on the Ticket Details page.ġ2. In ‘Post session details:’ select the radio button ‘as XML data’.ġ1. Enter the URL copied in step 9 in ‘Post session details to URL when session is ended by a technician:’ĭ. Select a Technician Group and go to ‘Settings > Exporting Session Data.Ĭ. Go to LogMeIn Rescue and open the Administration Center.ī. Set Rescue to export session data to Freshdesk. Click on the settings icon next to ‘LogMeIn Rescue’ appĩ. In your Freshdesk account, go to Admin > Appsħ. Set your SSO password under ‘Single Sign-On’ in the field ‘Enter new SSO password.’Ħ. Go to LogMeIn Rescue and open the Administration center.Ĭ. ![]() Your Company ID is located under ‘Single Sign-On’ in the section called ‘ASP. In the Administration Center, go to ‘Global Settings’Ĭ. Go to LogMeIn Rescue and open the ‘Administration Center’ ī. Enter your Freshdesk Domain name and API key and click ‘Authenticate’.ģ. To integrate LogMeIn Rescue with Freshdesk, go to Admin > Apps > Get More Apps > LogMeIn RescueĢ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |