[MAGNOLIA-3725] User database separate Created: 02/Jun/11 Updated: 21/Jun/11 Resolved: 21/Jun/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.4.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Jose Ramon Rodriguez | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
We separated the public user workspace on a database that is accessible from several publics systems. This can affect the the UserRoles or usergroups. Thanks |
| Comments |
| Comment by Zdenek Skodik [ 02/Jun/11 ] |
|
Could you please elaborate a bit more about your use case? Should we consider this as a bug, feature or support request? Basically there is no such workspace, public users are stored in the users workspace, within the public tree (the workspace is defined in repository.xml, Magnolia CMS doesn't interact with underlying DB directly, but always via standardized JCR interface). The PUR code tries to resolve such user from there. Also IIRC there are no groups/roles assigned to public users directly. |
| Comment by Philipp Bärfuss [ 21/Jun/11 ] |
|
I don't think this is an issue as this is already possible. Please comment if I am wrong. |