Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvement for managing https endpoints #162

Open
maephisto666 opened this issue Aug 12, 2020 · 0 comments
Open

Improvement for managing https endpoints #162

maephisto666 opened this issue Aug 12, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@maephisto666
Copy link
Contributor

At the moment all the endpoints listed in the various application-*.yml files are based on plain http. There is a growing need to run bb-fuel against the same secured endpoints (using https).

It would be nice to have an option to force https on

  • all the endpoints
  • or at least a subset of them (specifically the ones that are meant to be publicly exposed. See below).

In a typical setup you have indeed 2 different kinds of endpoints:

  • the ones which are meant to be consumed by the outside world (i.e. identity, gateway, auth);
  • the ones which are meant to be consumed from within the bank/organization, therefore usually exposed on http (e.g. registry, tokenconverter, accessgroup, etc.).
@maephisto666 maephisto666 added the enhancement New feature or request label Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant