If you have SSO enabled then the authentication is done on every page. Can you please explain the issue in more detail? What do you mean with “logged out pages”?
Well, for example, some of this site is public. The front page, contact info, etc. All open to the public.
If, as an example, we use a different security tool, we can then set the entire set “default” for view only when logged in, and then on individual pages, we can set security to “public”. This allows us to show pages even when not logged in.
So, we want the AD1 to be our point of authentication, and it does, but we don’t want it to blanket restrict the entire site without some options.
Including this as one example, but others are similar. If I use this plugin, I can make the site private, and then modify specific pages as needed based on logged in/out status, and even member role.
http://screencast.com/t/6Yi3pUmdAmi
Your AD1 is perfect for allowing me to use AD as my source of authentication, but it also seems to be dominating the site security so that no other plugin can then control the content.
In our use, we want you to log us in, then let us use our in/out statues and role, so other tools can control our experience.
We had already looked into getting ADI to work with Ultimate Member plug-in. As far as I can see from our issue tracker Ultimate Members returns internal data from the “authenticate” filter not in an WordPress-expected way.
I am not sure when and if we can fix this. If you really need it, please feel free to contribute a PR or receive a quote from us.
In our case, we aren’t using Ultimate Member, it was simply one of the programs we’ve looked at so far. What membership programs does ADI work with, we’re happy to look at them.
I had the time to take look into this because we had implemented NADI support for UM yesterday. I tried the settings you described with NADI 2.0 enabled:
– SSO disabled
– NADI UM extension disabled
– A non-logged in user can access a UM page/blog post with UM access set to “Everyone” or “Public”
– A logged in user can access a UM page/blog post with UM access set to “Everyone” or “Public”
– A non-logged in user can *not* access a UM page/blog post with UM access set to “Content accessible to Logged In Users*
In addition to that NADI does not interfer with the permission of pages. It does only handles the authentication, authorization and role assignment during login. Finer grained access settings are not the scope of our plug-in.
What NADI does is to infer with the authentication. This is the cause we developed the UM extension. As already written – and seen in the last days – at least UM does a lot of magic during authentication which makes it impossible to be compatible with “vanilla” NADI.
We will release NADI 2.0.11 in the next weeks and along to this the UM extension.
