Bearer

Use bearer middleware to secure HTTP endpoints by verifying bearer tokens

The bearer HTTP middleware verifies a Bearer Token using OpenID Connect on a Web API without modifying the application. This design separates authentication/authorization concerns from the application, so that application operators can adopt and configure authentication/authorization providers without impacting the application code.

Component format

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4.   name: bearer-token
  5. spec:
  6.   type: middleware.http.bearer
  7.   version: v1
  8.   metadata:
  9.   - name: clientId
  10.     value: "<your client ID>"
  11.   - name: issuerURL
  12.     value: "https://accounts.google.com"

Spec metadata fields

FieldDetailsExample
clientIdThe client ID of your application that is created as part of a credential hosted by a OpenID Connect platform
issuerURLURL identifier for the service.“https://accounts.google.com“, “https://login.salesforce.com“

Dapr configuration

To be applied, the middleware must be referenced in configuration. See middleware pipelines.

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Configuration
  3. metadata:
  4.   name: appconfig
  5. spec:
  6.   httpPipeline:
  7.     handlers:
  8.     - name: bearer-token
  9.       type: middleware.http.bearer

Last modified June 24, 2021: upmerge/06-24 (#1588) (55d9123c)