Skip to content
This repository has been archived by the owner on Dec 2, 2024. It is now read-only.

Service Broker should return a clearer response when bind fails because of Conjur connection issue #45

Open
izgeri opened this issue Feb 14, 2018 · 0 comments

Comments

@izgeri
Copy link
Contributor

izgeri commented Feb 14, 2018

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.

@izgeri izgeri self-assigned this Feb 14, 2018
@izgeri izgeri added ready and removed in progress labels Feb 22, 2018
@izgeri izgeri modified the milestones: There is an updated release of the TAS tile - Milestone 1, There is an updated release of the TAS tile - Milestone 2 Jul 6, 2020
@izgeri izgeri removed this from the There is an updated release of the TAS tile - Milestone 2 milestone Nov 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant