New Vendor Bridge offering for SaaS Shield #5
BobWall23
announced in
Announcements
Replies: 1 comment
-
Just a note to say that I'm pretty excited about this functionality because of the trends behind it. When we started the SaaS Shield product, it was for companies that wanted to offer enhanced security to a select few of their customers who were demanding things like Customer Managed Keys / Hold Your Own Keys. But we're seeing a trend where people want to provide that level of security to all of their customers whether they can hold their own keys or not. This is a great sign for the future of security in SaaS applications. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The administrative UI for our SaaS Shield product, the Configuration Broker (CB), allows SaaS vendors to manage their tenants interactively. However, many vendors (particularly those with a large number of tenants) need a programmatic way to manage tenants. We have create the Vendor Bridge to provide that functionality. The VB, like the Tenant Security Proxy (TSP), runs in the same infrastructure as your application. You create a service account in the CB in the same way that you create service accounts for TSPs. Once the VB is configured, started, and connected to CB, it provides a REST API your applications can use to perform vendor maintenance operations. Authentication is via an API key, in the same way that our tenant security client libraries authenticate with the TSP.
Documentation on the Vendor Bridge available here.
Beta Was this translation helpful? Give feedback.
All reactions