[OPENIG-4896] Documentation for JWTValidationFilter and IdTokenValidationFilter incorrectly describes how to supply JWTs for validation Created: 31/Aug/20 Updated: 03/Sep/20 Resolved: 03/Sep/20 |
|
Status: | Resolved |
Project: | Identity Gateway |
Component/s: | Doc |
Affects Version/s: | 7.0.0, 7.1.0 |
Fix Version/s: | 7.0.0, 7.1.0 |
Type: | Bug | Priority: | Major |
Reporter: | Tim Vogt | Assignee: | Joanne Henry |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||
Sprint: | 2020.12 - IG / Microservices | ||||||||
Story Points: | 1 |
Description |
The documentation for the aforementioned filters incorrectly states that the JWT/id_token to be validated needs to be supplied as a config expression, and suggests in the examples that the value should be statically configured in the route, while, actually, the idToken }}and {{jwt properties support runtime expressions, so that values can be picked up from the request as one would expect. |