Description
Follow-up to #8884. The cyberark-vault integration tests currently only exercise API key authentication. The component supports two additional authentication methods and a custom client injection that are not covered.
Missing Coverage
-
Username/password authentication — The component supports username + password credentials as an alternative to API key auth. Currently only API key auth (username + apiKey) is tested.
-
Pre-authenticated token authentication — The component supports passing a pre-obtained authToken directly, bypassing the login step entirely. Not tested.
-
Custom ConjurClient via registry — The component supports injecting a ConjurClient bean from the CDI registry, which skips all URL/account/auth validation. Not tested.
Description
Follow-up to #8884. The
cyberark-vaultintegration tests currently only exercise API key authentication. The component supports two additional authentication methods and a custom client injection that are not covered.Missing Coverage
Username/password authentication — The component supports
username+passwordcredentials as an alternative to API key auth. Currently only API key auth (username+apiKey) is tested.Pre-authenticated token authentication — The component supports passing a pre-obtained
authTokendirectly, bypassing the login step entirely. Not tested.Custom ConjurClient via registry — The component supports injecting a
ConjurClientbean from the CDI registry, which skips all URL/account/auth validation. Not tested.