• Resolved ericscoles

    (@ericscoles)


    Trying to use wpo365 on a shared multisite. Ideal use case would be for users to log in log in via Office365 using SAML SSO, which would create a user for them if one did not already exist; site admins would then subsequently add that user to subsites.

    Login works, user is created, but then cannot be added to subsites – attempting to do so returns the error message “The requested user does not exist.”

    If the user is created ahead of time, they can be added to subsites and will be able to SSO.

    Is there some step I’m missing in this?

    NOTE: In testing this I’ve determined that the username of the created user is in the form of an email (e.g. “[email protected]”), which does not appear to be a lawful WordPress username. Could that be the reason for the error?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter ericscoles

    (@ericscoles)

    No log entries appear to be generated by this failure.

    When the user is created, they’re created without an email address. I’ve tried adding an email address to the user; same result: “requested user does not exist” when trying to add to a subsite.

    Thread Starter ericscoles

    (@ericscoles)

    Following steps are required to add a user to a subsite after account has been automatically created on SSO:

    1. Edit newly created user to add email address (they will be created without one)
    2. add the user to the subsite USING THE EMAIL ADDRESS. No other matching method will work – you cannot pick them from the auto-lookup list, that will fail with ‘user does not exist’. ONLY the email address will work.

    Root cause seems to be that the user has been created without an email address. Not sure whether you regard that as a defect, but it would be good to document it as a requirement.

    QUESTION: what would we have to do in order to make sure that users got an email address if their account were auto-created on login? I.e. which plugins would we have to activate, which would have to be upgraded to premium, etc.

    Plugin Author Marco van Wieren

    (@wpo365)

    Hi @ericscoles

    Thank you for reaching out!

    By default, WPO365 will only add the user to the subsite they attempted to access initially. If they then navigate to another site, for example to the admin-dashboard, then they are indeed not automatically added as a member.

    The next update version 28.0 that is due next week will include a premium option that – if enabled – will automatically add a user that signs in with Microsoft to all subsites in the network.

    Alternatively, I believe you’ll find plugins that will do the job of adding a new member e.g. of the main site to all the subsites as well.

    Hope that helps!

    -Marco

    Plugin Author Marco van Wieren

    (@wpo365)

    Hi again @ericscoles

    I just noticed now the other question you have in regard to the email address. You’re right in that completing a user’s profile with their email address and (first, last and display) name details is a premium function. For example the PROFILE+ addon would accomplish this for you. If you need additional functionality like described in my previous reply – e.g. to add each user as a member to all subsites – then the LOGIN+ might be the better alternative (includes the PROFILE+ functionality).

    You can check our website for details about different packages and tiers.

    Please let me know if you have further questions or contact us directly via the contact form on the website.

    Hope this helps!

    -Marco

    Thread Starter ericscoles

    (@ericscoles)

    Thanks for confirming – right now we’re using free version because we’re still at prototype stage, a pricing related email to you all is on my to do list.

    Marking as resolved since I think I have either a workaround or explanation for everything in my original question.

    • This reply was modified 6 months, 2 weeks ago by ericscoles. Reason: typo
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Add user to subsite after creation at SSO: “The requested user does not exist”’ is closed to new replies.