Business Problem:

Government customer would like to send ACS notifications to their internal RocketChat communication platform.

Use Cases:

Due to security requirements, a secure RocketChat platform is utilized for a customer's internal communication and collaboration.  The customer wishes to send ACS notifications to a specific RocketChat channel.  Currently, the only *potential" way to implement such notifications would be to utilize the "Generic Webhook" integration and implement a cumbersome incoming webhook script in RocketChat (https://docs.rocket.chat/docs/integrations).  However, as RocketChat's api is Slack-compatible, an easier solution for the customer would be to point ACS's Slack Notifier Integration to their internal RocketChat service.  But restrictions in the existing Slack Notifier allow it to only point to Slack endpoints - likely as a result of https://issues.redhat.com/browse/ROX-9783. 

If a RocketChat Notifier Integration existed (based on the Slack integration as RocketChat's API is Slack-compatible), then the customer wouldn't have to configure and manage a custom incoming webhook script in their RocketChat environment.

Key Functionality:

Allow for the creation of a Notifier Integration similar to the existing "Slack" notifier integration and allowing for the destination webhook URL to be a customer's internal RocketChat service.

Benefits:

Customers leveraging RocketChat instead of Slack for internal communication due to security restrictions will be able to more easily implement ACS notifications to channels in the customer's RocketChat environment.

Acceptance criteria:

Successfully forward ACS notifications to a channel on a RocketChat server.