September 2022 brought with it the release of Solace PubSub+ Broker 10.1.1. Even though this release is a patch release from 10.1.0 it is the production release and brings with it a couple of new and useful features.
Sign up to Solace Academy to get access to our September 2022 Monthly Feature Highlight Training and read on to learn about the features you’ll be learning to implement.
REST delivery points (RDPs) have been a great feature for Solace PubSub+ Event Broker. They’ve allowed clients to more easily connect their existing REST APIs with their event broker without having to create a consumer to consume events and pass them on.
PubSub+ Event Broker v9.11 introduced the ability to add custom HTTP headers to outgoing RDP messages. This vastly changed the ways in which REST APIs could be used by RDPs. One caveat that came with this feature however was that all users that had access to the broker manager also had access to the values for these request headers. This becomes an issue when important and secret values like API keys or account passwords are passed in HTTP headers.
PubSub+ Event Broker v10.1.1 introduces the ability to add protected HTTP request headers to a Queue Binding for RDPs. With this feature you can define a collection of RDP Queue Binding header name/value pairs where the value is treated as a “protected” value, similar to how passwords are handled in the management interfaces in the broker configuration. This new collection is very similar to the existing collection of RDP Queue Binding headers/value, except the values in the new collection are always masked or omitted from display in the CLI, SEMPv2, or Broker Manager UI.
In the September 2022 Monthly Feature Highlight training you will learn how to use the Solace Broker Manager to create a REST Delivery Point that uses protected HTTP request headers.
OAuth is an incredibly popular and growing standard in APIs, which includes REST APIs. That’s why RDPs in Solace PubSub+ Event Broker have supported OAuth for REST consumers for quite some time now. But while the OAuth standard requires certain parameters be presented in the response for an access token request, the amount of time the token is valid is only recommended. Version 10.1.1 of PubSub+ Event Broker has a solution to when tokens don’t provide this.
In the September 2022 Monthly Feature Highlight training you will learn about how token expiration relates to the OAuth standard and the Solace broker as well as how to set the default token expiry configuration for a REST Consumer.