162dd87fc1
This PR fixes `encodeAssertion` to use btoa correctly for SAML assertions that contain non-ASCII. Messages are first manually encoded into UTF-8, and the resulting data is coerced into a JS string that btoa will correctly encode. That intermediary string isn't entirely meaningful -- JS strings are UTF-16, not UTF-8 -- but I think this "hack" of sorts is tolerable given how fleeting its use is. |
||
|---|---|---|
| .. | ||
| app | ||
| components | ||
| lib | ||
| pages | ||
| wordmark.svg | ||
