Rebar Endpoints

Monkton, Inc.

Rebar Endpoints are how Rebar enabled apps communicate with the world. These endpoints 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.

Our HTTP based web service integration, managed with Rebar Proxy connectors, enables your organization to directly integrate. The Rebar Proxy connectors can leverage JWT configuration to authenticate the users session. Additionally, the connector can be setup to enable token reuse (or limit token reuse) and indicate which user parameters to pass on to the JWT service.

Rebar Endpoints

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

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

Note The Rebar Hub will be migrating to new Rebar Endpoint management tools that will allow Rebar Endpoints to be managed easier.

It is important to note that these Rebar Endpoints can be limited to specific applications and specific HTTP methods. This enables the Rebar Endpoint 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.

Adding a Rebar Endpoint

Rebar Endpoints are how Rebar enabled apps communicate with the world. These endpoints 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.

Our HTTP based web service integration, managed with Rebar Proxy connectors, enables your organization to directly integrate. The Rebar Proxy connectors can leverage JWT configuration to authenticate the users session. Additionally, the connector can be setup to enable token reuse (or limit token reuse) and indicate which user parameters to pass on to the JWT service.

Rebar Endpoint Fields

Adding a Rebar Endpoint requires a few fields which can be later updated. These fields are:

  • Name: a friendly name for the endpoint
  • Description: a description for the endpoint
  • API Path: an internal mappable path for the endpoint (must be unique)
  • Greedy URL: allows for a /* path to consume everything below it
  • Forwarding URL: the URL that requests will be forwarded to
  • App Targeting: limits the apps that can access the endpoint
  • HTTP Method targeting: the HTTP method to point to
  • JWT Configuration: The JWT Configuration to leverage

Greedy URL

The Greedy URL allows for a * condition after a path. For instance, the API Path in an endpoint of myapp-dev may forward to the Forward URL value of https://myapi.something.com.

In this case, your Rebar API endpoint, https://api.example.com/myapp-dev/* would forward the request to https://myapi.something.com/myapp-dev/*.

You can also set the API Path Strip value, if we applied myapp-dev, it would take the request https://api.example.com/myapp-dev/* would forward the request to https://myapi.something.com/*.

Rebar Endpoint Security

It is important to note that these Rebar Endpoints can be limited to specific applications and specific HTTP methods. This enables the Rebar Endpoint 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.

Steps to Add a new Rebar Endpoint

Adding a new Rebar Endpoint is a simple process, follow below to create a new Rebar Endpoint

  1. On the Rebar Endpoints management screen, tap Add Endpoint
  2. Enter the name for the Rebar Endpoint - this should be something that quickly indicates the use of the Rebar Endpoint
  3. Enter a description for the Rebar Endpoint - this should be something descriptive
  4. Enter a mapped URL for the Rebar Endpoint - this will be the value embedded within the mobile app. See Rebar Endpoint Parameters below to understand how to map URL path values to the Forwarding URL
  5. Enter a Forwarding URL for the Rebar Endpoint - this is the URL that the request will be forwarded to
  6. Select HTTP method to listen for, for the Rebar Endpoint - this will limit the Rebar Endpoint to specific HTTP methods. This is useful when adding multiple endpoints that could have the same path
  7. Select the targeted App for the Rebar Endpoint - this will prevent authentication token crosswalk from app to app
  8. Select the JWT Provider for the Rebar Endpoint - this optional setting will ensure that the Rebar Endpoint will have an associated JWT provider

Modifying a Rebar Endpoint

In addition to adding Rebar Endpoints - they can be modified at any time by administrators. This will include updating meta data, Forwarding URL, and other fields.

Managing Rebar Endpoint

Rebar provides a few management methods to control Rebar Endpoints . Administrators can delete endpoints, disable endpoints, and enable or disable logging.

Deleting an Endpoint

To delete an Rebar Endpoints , tap the Delete Endpoint button and confirm the prompt. This action cannot be undone.

Endpoint Enablement

Endpoints can additionally be disabled by the administrator at and point in time. This will prevent access by mobile apps to the endpoint, so be very careful in the decision to disable an endpoint.

Rebar Endpoint Test Data

Rebar enables developers to create mock data that will return sample data to developers. This mock data hook will enable developers to rapidly build apps that may not have the requisite web services available.

At this time, the mock data service is limited to JSON and text based results. Future versions of Rebar will enable more advanced mock data to be delivered to developers.

Notes

It will take a short period of time (less than a minute) for the updates to propagate to the Rebar Hub API server due to caching.