The generated claim-headers don't seem to be url-encoded. For example if there is someone with the name 'Cem Özdemir', the resulting name-claim-header will simply be OAUTH2_CLAIM_name: Cem Özdemir. But Section 3.1 of the ARPA Internet Text Messages spec states that headers are always in US-ASCII encoding and anything outside of that needs to be encoded. This leads to errors i.e. when forwarding this header to a spring boot application with strict firewall activated.
Is there any way to turn on url-encoding for those headers? My current workaround is to just turn them off via OAuth2TargetPass headers=Off.
The generated claim-headers don't seem to be url-encoded. For example if there is someone with the name 'Cem Özdemir', the resulting name-claim-header will simply be
OAUTH2_CLAIM_name: Cem Özdemir. But Section 3.1 of the ARPA Internet Text Messages spec states that headers are always in US-ASCII encoding and anything outside of that needs to be encoded. This leads to errors i.e. when forwarding this header to a spring boot application with strict firewall activated.Is there any way to turn on url-encoding for those headers? My current workaround is to just turn them off via
OAuth2TargetPass headers=Off.