Marco van Wieren

Closing this issue since no more replies have followed in the last 2 months.

Sorry for the late reply. All communications mostly flows through my website or via email @wpo365.com and hence I’ve missed the WordPress forum.

Please have a look at the configuration guide https://www.wpo365.com/redirect-uri/. In your case the error reported is clear as it states that you must use an absolute URL for the redirect URI.

You can always get back to your side when you navigate to the WordPress login page e.g. https://www.yourwebsite.com/wp-login.php

You can then manually log in to your WordPress site and edit the WPO365 settings.

Sorry for the late reply. All communications mostly flows through my website or via email @wpo365.com and hence I’ve missed the WordPress forum.

Question is: will this plugin connect directly to the O365 login page, so all I need to do, to login to the new WP site is to have O365 account, same as the one I am using for my work (e-mail, etc.)?

Yes, you will be able to log on to WordPress using your O365 login. The plugin will create a corresponding user for you to enable a Single Sign-on experience.

Have a look at the website https://www.wpo365.com where all features are thoroughly explained.

Closing this issue since no feedback has been received.

The Expired exception is an indication for your server believing that the authorization token that was received from Microsoft has expired. This can be the case when your server clock is skewed. The leeway setting defaults to 300 (seconds) to add some thresholds to this. Please check your server time first, then play around with the leeway setting. In the meantime I’ll have a look and make sure the class-not-found exception is fixed. However, the exception in itself makes clear that the token is rejected so from your end you can try and make sure that this is fixed as well.

Closing this issue as no further input has been received.

Tested the 2FA scenario and as expected the plugin continues to work as expected.

Closing this issue as the idea has been added to our roadmap.

We have added this idea to roadmap for Q2 2018.

Hi, Please make sure that you have installed the Redux Framework plugin. You should see instructions to do so, when installing the wpo365-login plugin, which is documented on our website.

I’m closing this issue as it is a duplicate of this issue on github.

Hi, can you please have a look at the issue logged at github. Currently, we are not aware of the plugin not working, but we haven’t tested it extensively.

Sorry that I’ve not reacted any sooner. Most support issues are actually tracked at github https://github.com/wpo365/wpo365-login/issues or as comments on the website https://www.wpo365.com.

No, currently this scenario is not supported. It would, however, not be too difficult to implement. If you’d need such an extension, feel free to contact me at [email protected].

Sorry that I’ve not reacted any sooner. Most support issues are actually tracked at github https://github.com/wpo365/wpo365-login/issues or as comments on the website https://www.wpo365.com.

I am afraid I don’t understand, how an Office 365 instance would be internally?

Sorry that I’ve not reacted any sooner. Most support issues are actually tracked at github https://github.com/wpo365/wpo365-login/issues or as comments on the website https://www.wpo365.com.

I haven’t tested a 2FA scenario. But I guess that when 2FA is enabled a user, when asked to log on, will be asked first for User Name and Password and second to enter a code. This, however, would be done whilst the user is login.microsoft.com. This has little or nothing to do with the plugin it self. The plugin redirects the user to login.microsoft.com and waits for that user to come back and bring an Open ID token. 2FA would not change this high level flow but instead would only send the requested confirmation and ID token after a 2FA has been succesfully processed.