This post is slightly copied from my own post in the #jupiter-beta channel in Slack.
I know there has been planned permission changes according to https://github.com/edx/edx-platform/blob/open-release/juniper.alpha1/lms/djangoapps/courseware/docs/decisions/0002-permissions-via-django-rules.rst
I am trying to get my head around it trying to figure out why one of my non-administrative user has absolutely no access to the contents of all his courses (or about pages for these same courses) while an administrative account has no issue. Is there a specific setting to allow course access for all users now? It definitely looks like a permission issue.
Based on the courseware decisions mentioned above, shall I assume we need a tutorial on bridgekeeper? Maybe I am totally wrong too…
When in doubt, I always go back to a default single server installation with the open-release branch of edX. It allows me to see if the behaviour in our fork is different than the behaviour with that branch.
In this case, I see the Demo Course in the catalog. I cannot see the about page when I click on the course. The users staff, audit, honor and verified are all registered in this course. All have the course in their respective dashboard. Only the user staff can access the contents of the course. The other users get “The page that you were looking for was not found. Go back to the homepage or let us know about any pages that may have been moved at firstname.lastname@example.org.” Also, only the staff user can see courses/course-v1:edX+DemoX+Demo_Course/about and only if authenticated.
What am I doing wrong? At least I know the problem does not seem to be related to our fork of Open edX only because I was able to replicate it in a single server installation with the open-release/juniper.alpha1 from edX.
Any suggestions or pointers that could allow me to have users access their courses?
Shall I open a CRI (Community Reported Incident) ticket in JIRA?