Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter katjmars

    (@kmarschner)

    @gtsiokos – thanks for the feedback. The issue is the latter: Users who are not logged in attempt to visit a protected page. Because they are not logged in they are redirected to a page explaining why they can not see the protected page. From that explanation page we provide a link to our custom login page. After they log in and try to visit the protected page they are still redirected to the explanation page, presumable because browsers are loading a cached version of the page. The default WP login page is not an option for us.

    Thread Starter katjmars

    (@kmarschner)

    @proaktion – I was able to narrow down what appears to be the problem using some of your suggestions in creating a native user from the WordPress side.

    It appears that when users log into our website using our SSO solution, regardless of the Groups they’re assigned to, the Groups page restriction is not being applied as expected.

    When the same user logs in using the ‘/wp-login.php?wpe-login=true’ link the Groups page restrictions are applied.

    Thread Starter katjmars

    (@kmarschner)

    Thanks for the response @eugenbleck.

    Agreed we feel like things should be working as expected but we haven’t had much luck. We added a new test page and assigned a new group to the Read option on the page.

    I did confirm that the capabilities included only ‘read’ and also added in the ‘read’, ‘read_private_pages, and ‘read_private_posts’.

    Confirmed that the user was added to the Group – and in fact that the user was the only member of the Group. Navigated back to the page and it was unable to be displayed with our standard “Not Found. Sorry, but the page you were trying to view does not exist.” message.”

    If I remove the Group from the Read menu which Restricts the visibility of this Page to members of the chosen groups, then the page becomes visible again.

    I did confirm that we have Groups v2.16.2 and unfortunately turning on Debugging doesn’t provide much insight. There are no references to any conflicts, notices or warnings that we’ve not seen before.

    Thread Starter katjmars

    (@kmarschner)

    If we remove the group(s) in the “Read” the pages become visible to anyone. We’ve tried with multiple groups, multiple users and different combinations

Viewing 4 replies - 1 through 4 (of 4 total)