Syntax
membrane:
src: <string> # required
'$ref': <string>
claims: <string>
claimsIdt: <string>
clientAuthorization: client_secret_basic
clientId: <string>
clientSecret: <string>
httpClientConfiguration: <string>
internalSrc: <string>
jwksRefreshInterval: <int>
registration: {}
responseModesSupported: <string>
scope: <string>
ssl: {}
subject: <string>
useJWTForClientAuth: <boolean>
membrane:
src: <string> # required
'$ref': <string>
claims: <string>
claimsIdt: <string>
clientAuthorization: client_secret_basic
clientId: <string>
clientSecret: <string>
httpClientConfiguration: <string>
internalSrc: <string>
jwksRefreshInterval: <int>
registration: {}
responseModesSupported: <string>
scope: <string>
ssl: {}
subject: <string>
useJWTForClientAuth: <boolean>
Attributes
| Name | Required | Default | Description | Examples |
|---|---|---|---|---|
| $ref | false | - | Reference a component defined under components. | - |
| claims | false | - | claims that are requested for the userinfo endpoint | - |
| claimsIdt | false | - | claims that are requested for the id_token | - |
| clientAuthorization | false | client_secret_basic | Client Authorization method (see OIDC Core 1.0 chapter 9 | - |
| clientId | false | - | - | - |
| clientSecret | false | - | - | - |
| httpClientConfiguration | false | - | - | - |
| internalSrc | false | - | - | - |
| jwksRefreshInterval | false | - | - | - |
| responseModesSupported | false | form_post query fragment | Comma- or blank-separated preference list of response modes (highest priority first). Example: | - |
| scope | false | - | - | - |
| src | true | - | - | - |
| subject | false | - | - | - |
| useJWTForClientAuth | false | - | - | - |
Child Structure
| Element | Cardinality | Description |
|---|---|---|
| registration | 0..1 | |
| ssl | 0..1 | Configures a TLS context: the identity (key and certificate) presented to the peer, the certificates trusted from it, and handshake parameters such as protocol, ciphers, and client-certificate policy. Attach it to a serviceProxy/api to terminate inbound TLS, or to a target to make an outbound connection over TLS; most attributes and child elements apply to both directions, but a few - such as clientAuth and useAsDefault - only take effect on an inbound context. See tutorials/ssl-tls/10-TLS-Termination.yaml for inbound termination and tutorials/ssl-tls/20-Central-SSL-Config.yaml for sharing one ssl across several APIs via $ref. |