log-cache-cf-auth-proxy job from log-cache/2.6.10
Github source:
5de93cc
or
master branch
Properties¶
cache_expiration_interval
¶
The expiration lifetime assigned to new cache entries
- Default
60s
cc
¶
ca_cert
¶The CA for the internal api
common_name
¶The CN for the CA cert
external_cert
¶
The TLS cert for the auth proxy
external_key
¶
The TLS key for the auth proxy
metrics
¶
ca_cert
¶TLS CA cert to verify requests to metrics endpoint.
cert
¶TLS certificate for metrics server signed by the metrics CA
key
¶TLS private key for metrics server signed by the metrics CA
port
¶The port for the auth proxy to bind a health endpoint
- Default
6065
server_name
¶The server name used in the scrape configuration for the metrics endpoint
proxy_ca_cert
¶
The CA used to sign the certificates that the reverse proxy uses to talk to the gateway
proxy_port
¶
The port for the cf-auth-proxy to listen on
security_event_log
¶
When provided, the path to a file where security events will be logged
skip_cert_verify
¶
Whether to accept invalid certs
- Default
false
token_pruning_interval
¶
The interval at which expired tokens are purged from the cache
- Default
60s
uaa
¶
ca_cert
¶The CA for internal UAA api
client_id
¶The client id to authenticate to UAA
client_secret
¶The client secret to authenticate to UAA
internal_addr
¶The endpoint used for the internal UAA api
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/log-cache-cf-auth-proxy/
directory
(learn more).
config/bpm.yml
(frombpm.yml.erb
)config/certs/cc_ca.crt
(fromcc_ca.crt.erb
)config/certs/external.crt
(fromexternal.crt.erb
)config/certs/external.key
(fromexternal.key.erb
)config/certs/metrics.crt
(frommetrics.crt.erb
)config/certs/metrics.key
(frommetrics.key.erb
)config/certs/metrics_ca.crt
(frommetrics_ca.crt.erb
)config/certs/proxy_ca.crt
(fromproxy_ca.crt.erb
)config/certs/uaa_ca.crt
(fromuaa_ca.crt.erb
)config/prom_scraper_config.yml
(fromprom_scraper_config.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.