Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Well, what’s interesting about that… is that Authorizer is creating users with <username>@<domain> … rather than just <username> … and it appears to be assuming that <username>@<domain> is also the email address… which it isn’t. I can’t imagine that our CAS is actually feeding the email address.

    The reason that this was an issue I think is that my CAS user was already in there with real email…

    <username> = <realemail>@<domain>

    and after patching, Authorizer created:

    <username>@<domain> = <username>@<domain>

    as the username + email pair … should Authorizer be assuming email address if CAS doesn’t feed that back?

    Sure… I grabbed the headers and sanitized my credentials. I’d rather send these to you directly, if possible.

    We’re running CAS 3.5.2 presently. Also, after turning on some PHP debug… I get this at the top of the screen after returning from the CAS login:

    Notice: Undefined variable: approved_user in /content/html/semtest/wp-content/plugins/authorizer/authorizer.php on line 685

    Again, WP tells me:

    Cannot create a user with an empty login name.

    I’m seeing the same issue on my setup… and I know that I have the correct CAS info… because if I switch to using a different CAS plugin called “CAS Maestro” with the same CAS details… it works perfectly.

    I don’t even seem to be being redirected to the CAS login page. When I click “Sign in with…” button, it doesn’t go anywhere just tells me “Cannot create a user with an empty login name.” I’ve made sure that my CAS session is destroyed… so, it shouldn’t be getting anything from an old session.

    What can I do to help debug this?

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