You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click on menu item to go to Datasets, Maps, Geostories, Dashboards, etc
Continue browsing site acting as normal
Actual Behavior
On front page of site, log in as admin user.
Click to go to Datasets page
On datasets page, standard icon which shows when user is logged in switches back to "Sign In".
Steps to Reproduce the Problem
Log in as user on front page
Click on Datasets page link
See that icon has changed back to "Sign In"
Specifications
GeoNode version: 4.2.3
Installation type (vanilla, geonode-project): vanilla
Installation method (manual, docker): manual
Platform: ubuntu 22.04
Additional details: This condition also appears to work in reverse. If you are on the datasets page, for example, and are logged in, then switch back to the main page, it will bring up the Sign In link again. I don't know if it is related, but I am also not getting the links to allow for adding resources to any of the sections, and this is when using the admin account which is superuser.
Looking at the geonode.log, shows that when switching from one to the other of the content sections, the GET command returns HTTP 200. When you switch from a content page to the home page, there are a couple of items which return 403 errors. I will add a text file of the log entries when the menu switch occurred.
The urls returning 403 errors were
/proxy/?url...........
/api/o/v4/userinfo
@imperialbeachca since you install geonode manually (i guess starting from the geonode core) did you install all the initial fixtures needed? I'm talking about:
Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
Specifications
Looking at the geonode.log, shows that when switching from one to the other of the content sections, the GET command returns HTTP 200. When you switch from a content page to the home page, there are a couple of items which return 403 errors. I will add a text file of the log entries when the menu switch occurred.
The urls returning 403 errors were
/proxy/?url...........
/api/o/v4/userinfo
Geonode_Log_Errors.txt
The text was updated successfully, but these errors were encountered: