Remedy integration steps required?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Remedy integration steps required?

L4 Transporter
11 REPLIES 11

L6 Presenter

Plz go through the provided link;

 

https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/TicketingIntegrationBMCRemedy.htm?Highlight=Remedy%20integration

L4 Transporter

Plz go through the provided link;

 

https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/TicketingIntegrationBMCRemedy.htm?Highlight=Remedy%20integration

L5 Sessionator

Bellow are the steps for ServiceNow, but I think you can try similar thing for Remedy

Requirements for SNOW integration :

1.ServiceNow account which has permission to see tickets in the ServiceNow.(read only access) - I tried to login with account as a test

2.URL and Port of ServiceNow RestAPI (port in the case if they changed the default one - 8443)

 

 

You need store SNOW account in the safe . i didn't create a new safe , i used the exist one PVWATicketingSystem ( no CPM assigned) and PVWAAppUser has access ( i add list , use , retrieve and under monitor too)

I duplicate windows domain account platform as WIN_DOM_ACC_SNOW (should be unmanaged platform)

I onboarded the SNOW account to

Safe: PVWATicketingSystem

Device: Operating System

Platform : my duplicated unmanaged platform (means plain , clean platform)

 

When you assign to platform you have two required field :

Username : SNOW account

Address typed domain name or URL (both ways worked)

 

After that just follow by instruction.

Worked for me .

Hi Nirmal- What if SNOW is on cloud say like in my enviroment it is Istanbul version.

Little confused with external module thing , any idea ?

Currently CyberArk supports Remedy and ServiceNow integration with some basic use cases. If you want to integrate with other ticketing systems(ex: CA, HP etc) , you can develop your own module and deploy in to your cyberArk solutions using the way explained in the external thing..

 

L4 Transporter
Hi nirmal Its Service now only but hosted on cloud , is there any detailed information I could get. Version is Istanbul. [cid:[email protected]] Vidit Goswami CYBERSECURITY & RISK SERVICES Wipro Limited Plot No.31 MIDC, Pune Infotech Park, Ph-2 Hinjewadi, Pune - 411 057 | India Sensitivity: Internal & Restricted

L5 Sessionator

10.6 supports all recent versions of ServiceNow including Istanbul.. just follow the Implementation guide ..

 

  • Geneva
  • Helsinki
  • Istanbul
  • Jakarta
  • Kingston

Hi Nirmal,

 

Whatever the steps provided from you, i have also done for the same with BMC. However Is that mandatory to run the Ticketing system on API Calls?

Our BMC is on SOAP Calls. So, if that is the case we can change the calls from SOAP to REST API and try to connect it.

Any suggessions

Hi @Nirmalkumar Dhanaraj​ is that only what you did? Just account integration? Is there anything at the configuration level that we need to do? A user guide will be helpful.

its a very straight forward integration.. nothing much to do.. follow the steps and you are done..

  • Make sure communication is there between PVWA and Ticketing system
  • ServiceAccount (I've mentioned required rights in some other post)

https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Configuring-Dual-Control-together-with-Ticketing-Integration.htm?tocpath=Administration%7CComponents%7CPassword%20Vault%20Web%20Access%7CConfiguration%7C_____9

  • 606 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!