Problem in Remedy integration

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

Problem in Remedy integration

L4 Transporter

The OOTB BMC Remedy integration for ticketing checks includes config for Change and Incident but not Problem are there plans to introduce this into the configuration in the future?

Are there any plans to standardise the 3 checks against the 3 main ticket types CR, INC and PRB?

Needing to check PRB seems to lead down a path of customised dll then integrating into PVWA from day 1?

 

13 REPLIES 13

L4 Transporter

Currently the BCM Validation happen based on the information in the below link:

 

https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/pasimp/ticketingintegrationbmcr...

If you need anything additional then you can request for new develpment and will need our custom extension team to develop it and it’s a charged service. or alternatevily you also develop the same using the external ticketing framework -

 

https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/integratewithexternalticketingsystem.htm#Develop

 

 

There is a similar request as ER https://community.cyberark.com/s/article/Additional-methods-for-BMC-Remedy-ticket-validation-VQA2 that you can follow and vote.

L4 Transporter

Currently the BCM Validation happen based on the information in the below link:

 

https://docs.cyberark.com/privilege-cloud-standard/latest/en/content/pasimp/ticketingintegrationbmcr...

If you need anything additional then you can request for new develpment and will need our custom extension team to develop it and it’s a charged service. or alternatevily you also develop the same using the external ticketing framework -

 

https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/integratewithexternalticketingsystem.htm#Develop

 

 

There is a similar request as ER https://community.cyberark.com/s/article/Additional-methods-for-BMC-Remedy-ticket-validation-VQA2 that you can follow and vote.

L4 Transporter

Whilst I get the options for a new development as well as the external dll option would be good to have problem alongside change and incident which are already there.

 

Is there some logic I am missing for the reason problem isn't considered?

Our deployment is self hosted PAM too.

I am following the other ER so thanks for that.

L4 Transporter

Hi @Stephen Clarke​  Did you try to configure

IN BMC Remedy > Ticketing Parameters> System Configuration

--> IncidentTicketFormat = ^PRB[0-9]*

 

L4 Transporter

Hi @Stephen Clarke​  Did you try to configure

IN BMC Remedy > Ticketing Parameters> System Configuration

--> IncidentTicketFormat = ^PRB[0-9]*

 

L4 Transporter

This is more to keep the context of the integration clean with respect to the ticket being raised and its context within Remedy.

Also under the covers of the capability wont specific API calls being made to the incident, change or problem module and therefore putting a PRB to an incident API will no doubt fail?

L4 Transporter

absolutoly right. but it may not be looking into the incident or change table but in a ticket table which can return success. ultimately , the custom development may be the way forward.

L4 Transporter

absolutoly right. but it may not be looking into the incident or change table but in a ticket table which can return success. ultimately , the custom development may be the way forward.

Hi @Stephen Clarke​ 

 

The custom integration would be a great choice which will cover all your customise ticket validation rules. In my experience having implemented custom ticketing system approval has worked better.

 

Hope it helps !

 

L4 Transporter

Wee are coming to the conclusion that custom dev is the way forward for this which is a completely different scenario to the implementation of the OOTB integ, for one who is going to do the customised development(which team would be best suited to do this work) to then be able to integrate into PVWA following the documented guidelines,

L4 Transporter

Hi @Stephen Clarke​  Any one having basic knowledge on .Net framework with C# should be able to do it.

L4 Transporter

Hi @Stephen Clarke​  Any one having basic knowledge on .Net framework with C# should be able to do it.

L4 Transporter

Also on this Remedy integration is any aware of the integration is logged in anyway into the EPV central auditing? Are the validation attempts logged anywhere within the standard OOTB reporting? to enable the reporting of service usage type stats?

 

  • 115 Views
  • 13 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!