/.well-known/jwks.json output wrong keys

[singlewind]

Describe the bug
The well known endpoint will expose the both public key of hydra.openid.id-token and hydra.jwt.access-token

To Reproduce
Steps to reproduce the behavior:

1. Run the docker version of oryd/hydra:v1.0.0-rc.9_oryOS.10
2. Open postman or any browser, visit http://[your_server]/.well-known/jwks.json
3. Will get a duplicate key of hydra.openid.id-token, instead of both keys of hydra.openid.id-token and hydra.jwt.access-token

Expected behavior
The endpoint return both keys of hydra.openid.id-token and hydra.jwt.access-token

Screenshots
output of endpoint: .

keys in database: .

Version:

• Environment: [Docker]
• Version [oryd/hydra:v1.0.0-rc.9_oryOS.10]

Additional context
As documentation state, this endpoint will be affected by configuration and settings. We tried both with explicitly broadcast settings and use the default value. The behaviors are same.

     # use default value
      - STRATEGIES_ACCESS_TOKEN=jwt

    # or force the value
     - STRATEGIES_ACCESS_TOKEN=jwt 
     - WEBFINGER_JWKS_BROADCAST_KEYS:hydra.openid.id-token,hydra.jwt.access-token

[aeneasr]

Thank you! This is fixed on master already though :)

[singlewind]

@aeneasr great, waiting for another release.

[aeneasr]

The release is up already!

…

On 30. Apr 2019, at 00:42, Yue Zhou ***@***.***> wrote: @aeneasr great, waiting for another release. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.