Spring / Spring CredHub Interview questions
What is the difference between CredHubPermissionOperations and CredHubPermissionV2Operations?
Both manage access control, but they model it differently:
| CredHubPermissionOperations (v1) | CredHubPermissionV2Operations |
| Permissions attached directly to a credential name | Permissions attached to a path, which can include wildcards |
| No individual permission identity | Each permission entry has its own ID |
| Whole permission set replaced together | A single entry can be updated or deleted by ID |
V2 is the interface most new code should reach for: identifying each grant by its own ID means you can revoke one actor's access without touching anyone else's, and path-based rules let you grant an actor access to a whole family of credentials — like everything under /myapp/prod/* — in a single entry instead of one per credential.
Which permission interface supports path-based wildcards?
What does each V2 permission entry have that V1 entries don't?
More Related questions...
