Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Login state not being maintained when switching from home page to other menu pages #12194

Open
imperialbeachca opened this issue May 2, 2024 · 3 comments

Comments

@imperialbeachca
Copy link

Expected Behavior

  1. On front page of site, log in as admin user.
  2. Click on menu item to go to Datasets, Maps, Geostories, Dashboards, etc
  3. Continue browsing site acting as normal

Actual Behavior

  1. On front page of site, log in as admin user.
  2. Click to go to Datasets page
  3. On datasets page, standard icon which shows when user is logged in switches back to "Sign In".

Steps to Reproduce the Problem

  1. Log in as user on front page
  2. Click on Datasets page link
  3. 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

Geonode_Log_Errors.txt

@mattiagiupponi
Copy link
Contributor

@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:

sample_admin.json
default_oauth_apps.json
initial_data.json

Other info: #6954

@imperialbeachca
Copy link
Author

I performed the steps to Initialize Genode, as listed below. I'm pretty sure this script installs the 3 files you list above.

Initialize GeoNode

sudo chmod +x *.sh
sudo chmod -Rf 777 geonode/static_root/ geonode/uploaded/
./paver_local.sh sync

Is there something else that I needed to do?

@imperialbeachca
Copy link
Author

Following up. Does anyone have any idea what may be causing this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants