Spring / Spring CredHub Interview questions
Explain the internal working of Spring CredHub's mutual TLS auto-configuration on Cloud Foundry?
The important thing to notice is how little Spring CredHub itself actually does here: it doesn't generate, store, or manage the certificate at all. That's entirely the platform's job, handled before the app process even starts, via the buildpack's container security provider.
Spring CredHub's only real responsibility is deciding, at auto-configuration time, not to configure OAuth2 — because no OAuth2 properties are present — and building a RestTemplate that simply uses the JVM's default (container-provided) keystore and truststore for its TLS connections. CredHub, on its side, resolves the authenticated caller's identity from the certificate's subject and evaluates every subsequent request as that mtls-app:<guid> actor against the credential's permissions.
More Related questions...