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

User Profiles container permissions #159

Closed
tusmester opened this Issue Sep 11, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@tusmester
Member

tusmester commented Sep 11, 2017

If there is no Profiles container in the repository, it is created from code when the first user profile is created. The problem is that in this case permissions are not set correctly.

Expectations:

  • the Profiles container is created correctly, using the Content api, not the Node api
  • permission break is done on the container
  • the Administrators group gets full permissions
  • the global Owners group gets full permissions

Where to fix this: User.cs, line 587.

Actual Results:

If a new user is created she will be the owner of the related document library in the user profile workspace but the owner remains Admin on all the children items (in the case of dms.demo 'Sample-folder' and 'Sample-document.docx'), so if she logs in her doclib is empty.

@tusmester tusmester added the bug label Sep 11, 2017

@herflis herflis added this to the Sprint 155 milestone Mar 27, 2018

@tusmester tusmester modified the milestones: Sprint 155, Sprint 156 Apr 4, 2018

@tusmester tusmester modified the milestones: Sprint 156, Sprint 157 Apr 18, 2018

@tusmester tusmester modified the milestones: Sprint 157, Sprint 158 May 2, 2018

@tusmester tusmester self-assigned this May 2, 2018

@herflis herflis assigned herflis and tusmester and unassigned tusmester and herflis May 9, 2018

@tusmester tusmester modified the milestones: Sprint 158, Sprint 159 May 16, 2018

@herflis herflis closed this May 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment