An update on ActiveMQ and the IdentityIQ 8.4 Release

As part of the IdentityIQ 8.4 release, we've added two exciting new features: Access History and Data Extract. These features require a message broker, ActiveMQ, which is listed on our supported platform documentation found here.

After listening to customer feedback, we are exploring the following improvements:

1. Eliminating the need for ActiveMQ for Access History: We're considering passing the workload to task partitions, enabling us to orchestrate and run tasks in parallel across multiple IdentityIQ hosts/threads, thereby avoiding the use of ActiveMQ.

2. Expanding support for additional brokers for Data Extract: Currently, we support ActiveMQ Classic, but we're investigating support for different messaging systems such as JMS (Java Message Service). This will allow customers to use any broker supported by JMS, including ActiveMQ (Classic and Artemis), RabbitMQ, IBM MQ, AWS MQ, and Oracle's Open MQ. As part of this project, we’re also investigating a capability for customers to bring their own integration of non-JMS compliant queue messaging services and use it in IdentityIQ.

We wanted to share our future direction to help you plan the implementation of these features. We'd love to hear from you about which brokers you are using. This feedback will help us evaluate whether we need to expand our coverage for other message protocols such as Kafka or AMQP. Please drop a comment below with the message brokers you are familiar with or already using to help us prioritize.

You might also be wondering when we'll begin supporting JMS to give you the flexibility to use some of the brokers mentioned above. We're actively working on this and will provide an update here in the next few weeks as soon as we have a date.

Thanks,

Anchal Dube (IdentityIQ Product Management Team)