CAS throws error even though it works

  • Resolved webelaine

    (@wpgirl369)


    8 years, 10 months ago

    Hi Paul,

    We have CAS working on several sites through Authorizer. The actual login is working fine. Where we are running into problems is at line 2199, where $cas_url is set.

    Our server sends people through a series of redirects, and it also uses a non-standard port (https that is not on 8080). So even though we’re able to log in just fine, the separate admin_notices() function continually gives us a warning that the CAS server cannot be reached.

    Would it be possible in a future release for you to add an additional CAS configuration setting, something like “fLogin URL override”? If that is left blank, the plugin can continue on as usual and build the URL itself, but if that is filled, it would override $cas_url so that the check would come back with a 200 success and not trigger the admin notice. This would only be for the admin_notice() function.

    I am happy to email you specific URLs if that is helpful but would rather not post them in a public forum. 🙂

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

    (@pkarjala)

    8 years, 10 months ago

    Hi @wpgirl369,

    By default the admin_notices check should be using the port value set under the External Services tab. By default, line 2207 will check what this value is, and if the port is NOT 80 or 8080, it will attempt to connect via HTTPS by default.

    It would be good to check if the URL constructed in this function at line 2208 and 2209 matches the URL your CAS server expects to be contacted at.

    Ideally the check to see if WordPress can reach the CAS url is to send the request to the CAS url itself.

    If I’m misunderstanding the issue, please let us know!

    Plugin Author pkarjala

    (@pkarjala)

    8 years, 9 months ago

    Hi @wpgirl369,

    Following up on this issue; can you please verify if you’ve had any forward movement in testing?

    Thanks!

    Thread Starter webelaine

    (@wpgirl369)

    8 years, 9 months ago

    I’ve tried hard-coding what I think the URL is without much luck. If you could privately help me determine what URL it’s pinging, that might allow our CAS server team to make config changes.

    Plugin Author pkarjala

    (@pkarjala)

    8 years, 9 months ago

    After researching further with @wpgirl369, we have determined this issue to be caused when the CAS URL has a redirect to another server for the actual login processing. Because the response message is a non-200 response, it causes Authorizer to automatically presume the server cannot be reached.

    Will discuss how we choose to address this.

    Plugin Author pkarjala

    (@pkarjala)

    8 years, 9 months ago

    Have chosen to address this by accepting 300 response codes as valid presence of a responding CAS server at the provided CAS url. It is up to the system administrator to ensure that this is expected and acceptable behavior.

    Will be pushed live shortly with Authorizer 2.6.19.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘CAS throws error even though it works’ is closed to new replies.