For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Rosieodonell's avatar
Feb 18, 2020
Solved

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!

3 Replies

  • 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.

    • Rosieodonell's avatar
      Rosieodonell
      Icon for Cirrus rankCirrus

      Still having issues. Just wondering if anyone else has run into this?