Closed yegle closed 3 years ago
Hey @yegle - FYI, we had a release error with v0.12.2 which has been fixed. If you upgrade to v0.12.2 it should be commit hash 2060f4e
and not contain this regression.
I am unable to reproduce on master
or f3a9ab170b7c507a902cc286f381d3a4f82059f8 or 2060f4e29a3119aa242107bf04a3773f6465e4af
jwt_claims_headers: email,groups,user,iss
policy:
- from: https://verify.localhost.pomerium.io
to: https://www.verify.pomerium.com
allowed_domains:
- pomerium.com
- gmail.com
pass_identity_headers: true
Yes I did noticed two different docker images both labeled v0.12.2.
I pulled a new image and it now correctly passed identify headers to the back end.
Updating to 0.12.2 seems to cause the identity headers (
X-Pomerium-Claim-Email
andX-Pomerium-Jwt-Assertion
in my case) to be missing.Reverting to 0.12.1 fixed the issue.
Config I used: Environment variable:
Policy: