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

Problem with YAML config #198

Closed
aserrallerios opened this issue Feb 11, 2019 · 3 comments
Closed

Problem with YAML config #198

aserrallerios opened this issue Feb 11, 2019 · 3 comments
Assignees
Milestone

Comments

@aserrallerios
Copy link

aserrallerios commented Feb 11, 2019

Hello,

it looks like KrakenD is ignoring my JOSE block in YAML (not in JSON). This looks like a valid YAML, but the request returns 200 with no token (it should return 401).

version: 2
timeout: 3000ms
cache_ttl: 300s
host:
- "http://fake_api:8080"
extra_config:
  github_com/devopsfaith/krakend-gologging:
    level: DEBUG
    prefix: "[KRAKEND]"
    syslog: false
    stdout: true
endpoints:
- endpoint: "/{p1}"
  headers_to_pass:
  - Authorization
  backend:
  - url_pattern: "/{p1}"
    sd: static
    encoding: json
  extra_config:
    github.com/devopsfaith/krakend-jose/validator:
      alg: RS256
      jwk-url: "https://a.b.com/oauth2/default/v1/keys?client_id=xxx"
      cache: true
  concurrent_calls: 1
output_encoding: json

I'm actually not sure if I should post this in krakend-ce. Please close if this is not the right place.

@kpacha
Copy link
Member

kpacha commented Feb 11, 2019

hi, @aserrallerios

you are right, the parsed configuration has some malformed extra_config structs the system does not understand.

thks for the heads-up

@kpacha kpacha self-assigned this Feb 11, 2019
@kpacha kpacha added this to the 0.8 milestone Feb 11, 2019
@kpacha kpacha added the bug label Feb 11, 2019
@kpacha
Copy link
Member

kpacha commented Feb 11, 2019

it should be fixed at master, and will be included into the next release (0.8.0)

@kpacha kpacha closed this as completed Mar 6, 2019
@github-actions
Copy link

github-actions bot commented Apr 9, 2022

This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.

@github-actions github-actions bot added the locked label Apr 9, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 9, 2022
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

2 participants