I am trying to implement the miniorange oauth server on wordpress. The goal is to use the wordpress credentials to sign as SSO on a client.
So far I cannot seem to get it working.
I always see the encoded URL state component has backslashes added to it.
"https://eabo.gemeinde.de/sso-callback?code=CODE&state=%7B%5C%5C%5C%22sid%5C%5C%5C%22%3A%5C%5C%5C%22SID%5C%5C%5C%22%2C%5C%5C%5C%22url%5C%5C%5C%22%3A%5C%5C%5C%22https%3A%5C%5C%5C%5C%2F%5C%5C%5C%5C%2Feabo.gemeinde.de%5C%5C%5C%5C%2F%5C%5C%5C%22%7D"
which results in sso login failure with unkown error status.
When manually decoding the URL string with JS decodeURIComponent
https://eabo.gemeinde.de/sso-callback?code=CODE&state={\\\\\\"sid\\\\\\":\\\\\\"SID\\\\\\",\\\\\\"url\\\\\\":\\\\\\"https:\\\\\\\\/\\\\\\\\/eabo.gemeinde.de\\\\\\\\/\\\\\\"}
and remove the backslahes using replace(/\\/g, ”)
It results into
https://eabo.gemeinde.de/sso-callback?code=CODE&state={"sid":"SID","url":"https://eabo.gemeinde.de/"}
And this loggs in successfully. Which tells me the SSO client cannot handle payload with backslashes.
I want to know if it is the SSO Server or the wordpress adding the backslashes here.
Or has anyone experienced something similar ? I saw something similar in Stackoverflow post which states that json_encode adds backlashes.
I just need to confirm if it is a miniorange problem or wordpress
