FIWARE integration task#1

[ilarimikkonen]

APInf needs to expose two settings from API umbrella:

• global request settings: IDP App ID
• sub url settings: Required headers

see screencaps

[ilarimikkonen]

[ilarimikkonen]

screencaps are for illustration; changes via management API

[ilarimikkonen]

• we need a task for APInf UI

[preriasusi]

3552

[preriasusi]

Regex to be .* when writing Required Headers.

[preriasusi]

[preriasusi]

UI design there. Should it be grouped still under a "OAuth IDP settings" etc.?

[fdelavega]

The required headers stuff under the sub-url parameters is used to specify tenants of the different datasets which are registered using the sub-url settings.

In this regard, if the required headers functionality is going to be supported, then the method and URL regex for sub-urls need to be also supported

[matleppa]

@fdelavega About parameter Required Headers (RH).

• Is the goal that the parameter RH can be given separately for each HTTP method in sub-URL request settings? So for each method is needed following fields for parameters
• HTTP method (is also "any" needed as a method
• regex

• Required Headers

  @vinaytech Changes needed to current implementation according to answers.

[ilarimikkonen]

confirmed with Ficodes: we need to support all methods including "any". Supporting multiple rules for same method is optional. regex needs to be given separately to all methods once / method. Each setting group has three parameters, method (pulldown), regex (text field) and required headers (text field)

[ilarimikkonen]

please use this style of ui implementation, this is visible for example in nightly if you select "custom rate limits" in proxy settings

[ilarimikkonen]

setting can be placed after rate limits in the proxy setting UI. For initial implementation it can be visible all the time

[ilarimikkonen]

there is one "IDP App ID" per API

[Nazarah]

@vinaytech please add me as a reviewer when u create a PR for this issue. I'd like to check the UI.