Create Use Case Documentation
(DOCU-176)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Suzanne Deprez | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
Create a use case that will provide information and documentation needed in order to access a public instance without entering a password. This came up in the user list forum and will help to provide more information under System Management > Instances on what can be done with instances. A skeleton of this use case is provided at http://wiki.magnolia-cms.com/display/DOCU/Reading+public+instance+without+password. |
| Comments |
| Comment by Antti Hietala [ 01/Sep/11 ] |
|
I believe this is a misunderstanding. The root cause of the forum user's problem was the name of the WAR file. When deployed, the application was automatically configured as an author instance because of the way it was named. The resolution to this issue is not to adjust anonymous user permissions on the deployed instance but to rename the WAR file so it gets deployed as a public instance instead. Anonymous user permissions will be correct on a public instance. The mechanism is described in Using a single WAR file with multiple configurations. Read the article and, if it is not clear that the WAR name defines what kind of instance is deployed, edit it. Then close this ticket. |