Spring / Spring CredHub Interview questions
Explain the execution flow of credential interpolation for VCAP_SERVICES?
The reason this exists at all is that a CredHub-backed service broker doesn't want to hand an app's raw secret to the platform's binding metadata, which can end up logged, cached, or surfaced through cf env. Instead the binding contains a pointer — effectively "this credential lives at this CredHub name" — and it's only resolved to the real value in the single, authenticated interpolateServiceData() call.
Because that call is made with the app's own identity (mTLS or OAuth2), it only succeeds if the app already has read permission on the referenced credential — interpolation doesn't bypass CredHub's normal access control, it just batches the lookups for every reference in VCAP_SERVICES into one round trip instead of one per credential.
More Related questions...