The Shibboleth IdP V3 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP4 wiki space for current documentation on the supported version.
MetadataProviderHTTPAttributes
The following attributes are common to all HTTP metadata providers (i.e., DynamicHTTPMetadataProvider
and FileBackedHTTPMetadataProvider
).
An HTTP metadata provider includes a default implementation of the org.apache.http.client.HttpClient
interface. The attributes in the following subsections control the behavior of the default HTTP client. To override the default client implementation, configure the following attribute:
Name | Type | Default | Description |
---|---|---|---|
httpClientRef | Bean ID | A reference to an externally defined Spring bean that specifies an |
Use of the httpClientRef
attribute precludes the use of any and all of the HTTP attributes in the following subsections.
HTTP Connection Attributes
The following attributes apply to the HTTP connections obtained and managed by an HTTP metadata provider:
Name | Type | Default | Description |
---|---|---|---|
connectionRequestTimeout 3.3 | Duration | Depends on the provider type | The maximum amount of time to wait for a connection to be returned from the HTTP client's connection pool manager. Set to PT0S to disable. This attribute is incompatible with httpClientRef . |
connectionTimeout 3.3 | Duration | Depends on the provider type | The maximum amount of time to wait to establish a connection with the remote server. Set to PT0S to disable. This attribute is incompatible with httpClientRef . |
requestTimeout | Duration | Depends on the provider type | DEPRECATED: Use |
socketTimeout 3.3 | Duration | Depends on the provider type | The maximum amount of time to wait between two consecutive packets while reading from the socket connected to the remote server. Set to PT0S to disable. This attribute is incompatible with httpClientRef . |
HTTP Security Attributes
The following security-related attributes apply to any HTTP metadata provider:
Name | Type | Default | Description |
---|---|---|---|
disregardTLSCertificate | Boolean | false | If true, no TLS certificate checking will take place over an HTTPS connection. This attribute is incompatible with |
disregardSslCertificate | Boolean | false | DEPRECATED: Use disregardTLSCertificate instead. |
basicAuthUser | String | DEPRECATED: Use | |
basicAuthPassword | String | DEPRECATED: Use | |
tlsTrustEngineRef 3.1 | Bean ID | DEPRECATED: Use | |
httpClientSecurityParametersRef 3.3 | Bean ID | A reference to an externally defined Spring bean that specifies an org.opensaml.security.httpclient.HttpClientSecurityParameters instance, which consolidates all HTTP security parameters including advanced TLS usage. This attribute conflicts with and overrides any explicit TrustEngine implementation configured as an inline <TLSTrustEngine> element. See the HttpClientConfiguration topic for more information. |
HTTP Proxy Attributes
The following attributes configure an HTTP proxy for use with an HTTP metadata provider:
Name | Type | Default | Description |
---|---|---|---|
proxyHost | String | The hostname of the HTTP proxy through which connections will be made. This attribute is incompatible with | |
proxyPort | String | The port of the HTTP proxy through which connections will be made. This attribute is incompatible with | |
proxyUser | String | The username used with the HTTP proxy through which connections will be made. This attribute is incompatible with | |
proxyPassword | String | The password used with the HTTP proxy through which connections will be made. This attribute is incompatible with |
HTTP Caching Attributes
The following attributes configure an HTTP cache on an HTTP metadata provider:
Name | Type | Default | Description |
---|---|---|---|
httpCaching | "none" , "file ", or "memory " | Depends on the provider type
| The type of low-level HTTP caching to perform. There are three choices:
This attribute is incompatible with Some metadata providers, most notably the reloading "batch-oriented" providers, implement HTTP caching at a higher layer and tend to work best with |
httpCacheDirectory | String | If | |
httpMaxCacheEntries | Integer |
| The maximum number of responses written to cache. This attribute is incompatible with |
httpMaxCacheEntrySize | Integer |
| The maximum response body size that may be cached, in bytes. This attribute is incompatible with |