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.

Sign up for GitHub

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

Jump to bottom

Access rights EVERYONE is not propagated to GeoServer for authenticated users #200

Closed
jirik opened this issue Dec 22, 2020 · 0 comments · Fixed by #213
Closed

Access rights EVERYONE is not propagated to GeoServer for authenticated users #200

jirik opened this issue Dec 22, 2020 · 0 comments · Fixed by #213
Labels
bug Something isn't working
Milestone
Release 1.9

Comments

@jirik
Copy link
Member

jirik commented Dec 22, 2020 •
edited
Loading

Steps to reproduce:

  • create new layer as authenticated user, set read access for EVERYONE
  • logout
  • authenticate as another user
  • ask for published layer through WMS or WFS

GeoServer states that layer is not found.

Solution:
Propagate EVERYONE to GeoServer as ROLE_AUTHENTICATED + ROLE_ANONYMOUS (currently, only ROLE_ANONYMOUS is propagated). Or in case of EVERYONE use * and no other role.
@jirik jirik added the bug Something isn't working label Dec 22, 2020
@jirik jirik modified the milestones: E7, Release 1.10, Release 1.9 Dec 22, 2020
jirik added a commit that referenced this issue Jan 5, 2021
@jirik
Access rights EVERYONE is propagated to GeoServer for authenticated u…
7a4a3b3 
…sers

Fix #200
jirik added a commit that referenced this issue Jan 5, 2021
@jirik
Access rights EVERYONE is propagated to GeoServer for authenticated u…
8830d23 
…sers

Fix #200
jirik added a commit that referenced this issue Jan 5, 2021
@jirik
Access rights EVERYONE is propagated to GeoServer for authenticated u…
4f2d11e 
…sers

Fix #200
jirik added a commit that referenced this issue Jan 5, 2021
@jirik
Access rights EVERYONE is propagated to GeoServer for authenticated u…
bb004a3 
…sers

Fix #200
@jirik jirik closed this as completed in 319ff03 Jan 6, 2021
@jirik jirik mentioned this issue Jan 6, 2021
Merged
@index-git index-git reopened this Jan 7, 2021
@index-git index-git linked a pull request Jan 7, 2021 that will close this issue
Migration 1.9.0-1: recalculate GS security rules. #213
Merged
jirik added a commit that referenced this issue Jan 12, 2021
@jirik
Add info about #200 fix to changelog
e1596af
jirik added a commit that referenced this issue Jan 12, 2021
@jirik
Add info about #200 fix to changelog
0d58ae5
jirik added a commit that referenced this issue Jan 13, 2021
@jirik
Add info about #200 fix to changelog
6b80d11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Release 1.9
Development

Successfully merging a pull request may close this issue.

Migration 1.9.0-1: recalculate GS security rules. LayerManager/layman
2 participants
@jirik @index-git