• Resolved manakuke

    (@manakuke)


    We just switched to a new CAS service. That service automatically adds “@theirdomain.com” to the username to create the email instead of “@ourdomain.com”. We’re trying to clarify whats going on with the new CAS service (it’s through a third party called Unifyed that’s also providing SSO, portal, and mobile technologies for our school). But I have checked “Link CAS accounts to WordPress accounts by their username (leave this off to link by email address)” in Authorizer and thought this would prevent. It seems to be working with existing users (before checking, it was creating new/duplicate accounts). I just found one instance of a new student who’s account was created after activating the setting but pulled in “@theirdomain.com”. I’m guessing that is something that would need to be fixed on their end, but wanted to check on the Authorizer end.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Paul Ryan

    (@figureone)

    Is there any other attribute returned by CAS that has [email protected]? That would probably be the best scenario–then you just refer to that attribute in “CAS attribute containing email address” and that becomes the link between CAS accounts and WordPress accounts.

    Short of that, I can’t think of a clean way in Authorizer to treat all [email protected] usernames as [email protected] email addresses. You could maybe rewrite the database and change the domain name in each user’s wp_users.user_email field?

    Thread Starter manakuke

    (@manakuke)

    Thank you. I think that was the problem. I had the incorrect attribute in the “CAS attribute containing email” due to the change in CAS service. Thanks for your response and great plugin.

    Plugin Author Paul Ryan

    (@figureone)

    Great!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Possible Conflict with Link CAS accounts to WordPress accounts by their username’ is closed to new replies.