Forum Discussion
Rewrite Profile JSON error
Hey Everyone,
We are using a rewrite profile to do the following:
Converting
Client URI = https://customer.company.com/loginpage/
to
Server URI = https://login.company.com/
Everything looked fine but some users i guess have more access on the backend and are getting a JSON error. Should I be using Irules instead?
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!
- RosieodonellCirrus
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!
- RosieodonellCirrus
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.
- RosieodonellCirrus
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