Rebar Connectors

Monkton, Inc.

Rebar Connectors are an important part of configuring Rebar Endpoints - connectors provide a reusable means to connect to various backend systems.

Presently, we offer up a series of connectors:

  • Direct HTTPS Proxy
  • Amazon Web Service API Gateway
  • RedHat 3Scale
  • Mulesoft (Coming Soon)

Once a connector has been defined, it can be used within any Rebar Endpoint. By defining connectors, a series of Rebar Endpoints can be updated at once as certificates or authentication data changes. This ensures that having to update and manage security settings is abstracted away from the endpoint itself.

Connector Management

When browsing to the Rebar Connectors screen, administrators will be presented with the Rebar Connectors that have been configured within your Rebar Hub instance. From here, you can update an existing connector or add new ones.

The Rebar Connectors management screen also allows for the importing and exporting of Connectors enabling rapid migration from one environment to the other

It is important to note that these Rebar Connectors can be limited to specific applications. This enables the Rebar Connectors itself to be configured to disallow cross-walking of authentication tokens to ensure that bad actors can’t manipulate tokens from one app to another.

If app scope is defined for a specific connector, it will be the default for a Rebar Endpoint once an endpoint is using the connector.

Adding a Rebar Connector

Rebar Connectors are how Rebar Endpoints communicate with the world for authenticating connections. These connectors act as proxies to consume web service or communicate with our growing list of API management tools, like AWS API Gateway and RedHat 3Scale, as well as integrating directly with your existing HTTP based web services.

To add a new connector, on the Rebar Connectors Management screen tap “Add Connector” - this will prompt you to create a new connector.

Rebar Connector Fields

Adding a Rebar Connector requires a selection of the type of connector being generated. To being configuring your connector, select the type. Presently available are:

  • Direct HTTPS Proxy - invokes a web service directly, can have JWT configurations attached to it
  • Amazon Web Service API Gateway - invokes a AWS API Gateway
  • RedHat 3Scale - invokes RedHat’s 3Scale API provider
  • Coming Soon: Mulesoft - invokes Mulesofts API Provider

Once you have selected the type, the screen will automatically update with the appropriate details for the desired connector. Find the relevant section below on the connector details when configuring.

Adding a Direct HTTPS Proxy Connector

Monkton’s Direct HTTPS Proxy provides a mechanism to directly invoke web services with the Rebar Hub. These proxies can have JWT configurations enabled, providing a means to authenticate the web services calls. See the JWT Providers section for more information on configuring JWT providers.

Direct HTTPS Proxies require a few pieces of information:

  • Connector Name
  • Description
  • JWT Provider
  • App Scope

To configure this connector, follow below:

  1. Select the Connector Type of Direct HTTPS Proxy
  2. Enter the name - this should be something that quickly indicates the use of the Rebar Connector
  3. Enter the description - this should be something that is more descriptive of the use of the Rebar Connector
  4. Select the optional JWT Provider, this will invoke the JWT provider when the connector is used
  5. Select the optional App Scope, this will limit the apps that can invoke the Connector
  6. Tap “Save” this will create the connector and take you to the newly created connector

Adding an Amazon Web Service API Gateway Connector

Monkton’s AWS API Gateway Connector provides a mechanism to directly invoke AWS API Gateway endpoints with the Rebar Hub. These connectors leverage IAM credentials and API Access keys (or none) to invoke the web services. These configuration settings are stored within the connector. When the connector generates the request, it builds the authentication headers automatically and directs the requests to Amazon.

The AWS API Gateway Connector require a few pieces of information:

  • Name
  • Description
  • IAM Access Key
  • IAM Secret Key
  • API Gateway API Key
  • AWS Region
  • App Scope

To configure this connector, follow below:

  1. Select the Connector Type of AWS API Gateway
  2. Enter the name - this should be something that quickly indicates the use of the Rebar Connector
  3. Enter the description - this should be something that is more descriptive of the use of the Rebar Connector
  4. Enter the optional IAM Access Key and IAM Secret Key (you will need to provide both) to digitally sign the requests when made to the server
  5. Enter the optional API Gateway API Key which will automatically apply the API Gateway Key to the request
  6. Select the AWS Region that the AWS API Gateway resides in
  7. Select the optional App Scope, this will limit the apps that can invoke the Connector
  8. Tap “Save” this will create the connector and take you to the newly created connector

Adding a RedHat 3Scale Connector

Monkton’s RedHat 3Scale Connector provides a mechanism to directly invoke RedHat 3Scale endpoints with the Rebar Hub. These connectors the 3Scale API key to invoke the web services. These configuration settings are stored within the connector. When the connector generates the request, it builds the authentication headers automatically and directs the requests to RedHat 3Scale.

The RedHat 3Scale Connector require a few pieces of information:

  • Name
  • Description
  • 3Scale Secret Key
  • 3Scale Header Key
  • App Scope

To configure this connector, follow below:

  1. Select the Connector Type of Direct HTTPS Proxy
  2. Enter the name - this should be something that quickly indicates the use of the Rebar Connector
  3. Enter the description - this should be something that is more descriptive of the use of the Rebar Connector
  4. Enter the 3Scale Secret Key, this is obtained from your 3Scale portal
  5. Enter the 3Scale Header Key, which a default is provided. This indicates the key the HTTP Header will use to send the 3Scale Secret Key. The default is user-key
  6. Select the optional App Scope, this will limit the apps that can invoke the Connector
  7. Tap “Save” this will create the connector and take you to the newly created connector