• Resolved Ilene Johnson

    (@ilenejohnson)


    Our host is wepengine.com and we are getting a NOSTATE error when we login. I’m not sure if this is something with wpengine or our setup and at this point I don’t know what questions to ask or what to look for.

    Is this something to do with caching? I would appreciate any ideas about where to look or how to attack this problem and debug it. Its vexing.

    http://wordpress.org/plugins/saml-20-single-sign-on/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author ktbartholomew

    (@ktbartholomew)

    WPEngine doesn’t allow arbitrary PHP code to be executed from the plugins directory, which is required by the underlying SimpleSAMLPHP library. I started trying to troubleshoot this when I was using them once, but ended up just moving on. You should be able to get some suggestions from WPEngine’s support team about locations on the server where PHP execution is allowed, but you will officially be in unsupported “hack” territory at that point!

    Thread Starter Ilene Johnson

    (@ilenejohnson)

    I finally got your SAML plugin to work on WPEngine and the “NO STATE” was not having to do with WPEngine. It was an error coming back from the site we were trying to authenticate on. It just went away one day and we don’t know why.

    So, could you please explain what the “NO STATE” status even means?

    Plugin Author ktbartholomew

    (@ktbartholomew)

    NOSTATE is coming from SimpleSAMLPHP, see this link:
    https://code.google.com/p/simplesamlphp/wiki/LostState

    Thread Starter Ilene Johnson

    (@ilenejohnson)

    NOW I remember. We had to ask WpEngine to turn off their caching for this plugin. That is when it worked.

    But it will work on WPEngine.

    Plugin Author ktbartholomew

    (@ktbartholomew)

    That sounds about right. Thanks for letting me know!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘NOSTATE – wpengine’ is closed to new replies.