Hi,
I found another wierd behavior to get this error. And it is very annoying. Documentation sais that the SSO has to urlEncode the values of the unsigned payload.
Ok, for example I map the value of user.name:
- Single string. Works fine
- String with ONE space. It can either be encoded with a + or %20 (both are valid urlEncodings). Works fine
- String with TWO or MORE spaces. When they are encoded with a +, ERROR. With %20 works fine.
One space encoded with a ‘+’ works but several ‘+’ don’t? And the logs do not raise any error about this.
I think this is worth mentioning in the SSO documentation.
Thank you