Removing dependency on barb.hipch.at for HipChat Server Instances

[Jerry Qassar]

Just noticed this article after performing our upgrade to HCS 2.0:

https://confluence.atlassian.com/hipchatkb/data-that-is-sent-over-to-barb-hipch-at-how-can-admin-suppress-this-826877606.html

Part of the purpose of using the hosted solution is to minimize these handoffs to outside services (for file storage, attachment storage, voice chat, screen sharing, et cetera).  If we are already relaying through BARB on the appliance, are there any technical difficulties in relaying our push notifications directly to APNS/GCM (assuming a valid SSL certificate)?  If this is not possible, can we have an extra option to disable push notifications to mobile at the server level separate from the existing notification scrubbing option?  We do not have a problem with seeing message content on email notifications because that is all happening internally.

[Jerry Qassar]

To clarify:

barb.hipch.at seems to be an LB for incoming mobile notification requests.  Can we have a similar relay on the appliance?

[wdehaan]

Hi Jerry,

Thanks for posting this ask.

No, APNS/GCM certs are not directly configurable. 

I advise refusing outbound network access to barb.hipch.at in your own network infrastructure. The barb endpoint serves no other function than relaying mobile notifications.

barb.hipch.at does not log notification contents, though my word may not be enough for your infosec policies.