You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2024. It is now read-only.
At current, if you configure the service broker and then rotate the CONJUR_AUTHN_LOGIN user's API key without updating the configuration, on bind the error you receive will look like:
FAILED
Could not bind to service conjur
Error: Server error, status code: 502, error code: 10001, message: The service broker rejected the request to http://conjur-service-broker-loonies-linctus.local.pcfdev.io/v2/service_instances/aef5bf2c-d138-4dda-8f87-d15db8002b8b/service_bindings/484f3008-380c-4633-b909-e552036082c6. Status Code: 403 Forbidden, Body: {}
This error should be clearer, and should include a body that explains that the issue is that the Conjur configuration is no longer valid.
The text was updated successfully, but these errors were encountered:
At current, if you configure the service broker and then rotate the
CONJUR_AUTHN_LOGIN
user's API key without updating the configuration, on bind the error you receive will look like:This error should be clearer, and should include a body that explains that the issue is that the Conjur configuration is no longer valid.
The text was updated successfully, but these errors were encountered: