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

Edits showing up as anonymous #1490

Closed
jonpmarino opened this issue Aug 1, 2018 · 8 comments
Closed

Edits showing up as anonymous #1490

jonpmarino opened this issue Aug 1, 2018 · 8 comments
Assignees

Comments

@jonpmarino
Copy link
Member

in the edit history, it should show the username not "anonymous".

Screen Shot 2018-08-01 at 3.23.07 PM.jpg

@josellausas josellausas assigned josellausas and Coop56 and unassigned josellausas Aug 2, 2018
@Coop56
Copy link
Contributor

Coop56 commented Aug 2, 2018

This will be resolved once we get the automatic login working between geonode and geoserver.

@jonpmarino
Copy link
Member Author

interesting note - when I edit a geometry, its attributed to "anonymous" but when I 'revert' a change, it correctly attributes it to my username, aldoleopold
screen shot 2018-08-03 at 2 17 31 pm

@cuttlefish
Copy link
Member

The auth fix for styling didn't resolve this issue. It also doesn't work when logged in as admin.
It seems that it applies the username correctly when doing GeoGig API commands, but not when it does WFS-T edits.
I tried adding an access_token query parameter to the WFS-T request but it didn't seem to work.
Did this work in the past?

@cuttlefish
Copy link
Member

This works in Exchange. I'm not sure what they're doing differently. They're not assigning an access_token query param.

@jpierson-boundlessgeo
Copy link

If you do an authentication against GeoServer first, edits show up as the correct user.

@jpierson-boundlessgeo
Copy link

Seems to be an issue from WFS-T transactions not getting the correct user assigned. Also causes the same behavior in Append.

@jpierson-boundlessgeo
Copy link

The core issue is that our django templates completely overwrite the base GeoNode templates, which work because the permissions are handled within the template.

@lhcramer
Copy link
Member

lhcramer commented Dec 3, 2018

Verify 1822 addresses this issue

@cuttlefish cuttlefish removed their assignment Dec 12, 2018
@Coop56 Coop56 closed this as completed Dec 14, 2018
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

7 participants