When 'Intranet scenario is selected your plugin will secure both WordPress front- and backend and will try to authenticate what the user can effectively authenticate him or himself with Microsoft Azure Active Directory.
If this is the subject the user is granted access to page originally requested or center the user is deflected to the default WordPress login page..
Only when the user requests page from the backend e.g. wp-admin the plugin will try and verify the user using Azure Active Directory..
And in subject the user does so for the very time the plugin will create equivalent WordPress user for the first Office 365 users.
Also have look at this post if you need help to decide what or not our plugin can help you improve the user record when user try to gain accessing to financial intranet or internet WordPress site..
Added option to configure role for any WordPress user representing the Office 365 Azure AD created by the role is Subscriber.
Added option to configure preferred WPO365-login scenario and allowed default for two scenarios 'Intranet to secure both WordPress front- and backend and 'Internet to secure only the backend.
Changed the resource for license from id to Azure Active Directory allowing for need being supervisory plus added the application to shift the id configuratively..
Now the plugin decides to prepend https to the part based on the protocol used for the delete url.
This may cause the plugin to deflect the user to the page address starting with http instead of https and this soon may lead to the user being caught in password loop..
Read more
Related items:
