Redirect after CAS login

I experience something similar. We use a CAS plugin for authentication, and sometimes authenticated users are presented with the local wp-login page.

We haven’t found a way to avoid it, so I’ve just customized it to remove the fields. It confuses people, but I’m not sure how to prevent it.

Have a look at https://wpcassify.wordpress.com/getting-started/ and the Bypass CAS Authentication screencast, code and following notes.

This sends all login requests to wp-login, and you can customize your theme’s display to have a CAS Login button link. This is similar to the way the Authorizer plugin works by default.

I haven’t tried it with a custom login path, but assume it would work.

@sgoetz, because you are hiding the normal fields, adding the CAS Login link should be easy and might cause less confusion.

Thanks, @playgod.

I don’t think this will solve the issue. The problem isn’t that they can’t authenticate using CAS – this works fine. The issue is that once they are authenticated, they are sometimes prompted with the local wp-login page as though they are not already authenticated and have an active session with WP.

They shouldn’t be getting this page at all – but especially if they are already authenticated.

The current workaround is for them to logout and log back in using the admin login page for their blog (as opposed to logging in to the network).

Cheers,
Stephanie

@sgoetz Yes, I have been using a much older CAS plugin that sometimes has that problem, although it does completely take over the wp-login form for almost every WP action, including normal usage of the login/logout link in the old Meta widget. It seems to happen during some account maintenance functions and, of course, when the user follows a link in WP account notification emails.

I’m a new user of WP Cassify, so I’ll be interested to see if we experience a problem similar to what you describe.