Forum Discussion
Rewrite Profile JSON error
- Feb 25, 2020
So my access policy was the culprit because the access policy had a "SSO profile" configured on it. That is why i was getting the JSON error. So on the new connection based on the URI... i added:
WEBSSO::disable
now my problem is gone. yay!
Turns out it’s the access policy that causes the JSON error. When I add an I rule that disables the policy
ACCESS::disable
everything works fine. Is there something that I can add to the access policy to allow the JSON through without causing issues?
we don’t have the ASM module enabled.
Still having issues. Just wondering if anyone else has run into this?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com