-
Feature Request
-
Resolution: Done
-
Critical
-
None
-
2.6 ER1
-
None
-
8
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
3scale 2019-08-12, 3scale 2019-08-26, 3scale 2019-09-09, 3scale 2019-10-14
At the moment two new parameters for OpenID configuration are going to be added in APICast
proxy.jwt_claim_with_client_id that it's a string.
proxy.jwt_claim_with_client_id_type that defines if it's plain or liquid.
That will receive the JWT payload, and it'll render to get the client_id that the customer wants.
This task is blocked by THREESCALE-2264 and PR1034
See this comment
Dev notes
- This is only for OIDC integration in the proxy and belongs in the auth part of the form that shows when OIDC has been selected
- We should create 2 fields, a text input for the proxy.jwt_claim_with_client_id and a select for proxy.jwt_claim_with_client_id_type
- Add the 2 fields there underneath
- default values should be: plain & 'azp'
- If the selected proxy.jwt_claim_with_client_id_type is liquid, validate the syntax of proxy.jwt_claim_with_client_id
Probably APIcast is already validating it, but the configuration should also - Needs a migration to add 1 or 2 columns (need to be thought out carefully as we may end up adding more and more configuration to the proxy later)
- is blocked by
-
THREESCALE-2264 Make the JWT claim to get client_id configurable
- Closed