Ticket #997 (closed Defect: worksforme)
myDM webclient does not start when request is unauthorized
| Reported by: | Malte | Owned by: | |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.8.3 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.8.2 |
| Keywords: | Cc: | jri, JuergeN | |
| Complexity: | 3 | Area: | GUI / Usability |
| Module: | deepamehta-webclient |
Description
When requesting the dm4-webclient at https://my.deepamehta.de/ (being not logged in) I currently do get the following error message and the dm4-webclient is not properly initialized (even if i would i could not authenticate to go on).
Sorry! Fetching topic 8135 failed (java.lang.RuntimeException) Reason: user has no READ permission for object 8135 (de.deepamehta.core.service.accesscontrol.AccessControlException) Server status: 401 Unauthorized
Change History
comment:2 Changed 8 years ago by Malte
In the current myDM case it is the following GET request for which a "401" is returned:
comment:3 Changed 8 years ago by jri
IMPORTANT since DM 4.8.2: in the following situations you must delete the DM cookies (in particular dm4_workspace_id and dm4_topicmap_id) resp. restart the browser (which will delete the DM cookies anyways):
- when you connect to a different DM instance
- when you reset the DB
In these situations the IDs stored in the cookies are not valid anymore. This prevents the Webclient from launching.
If you delete the DM cookies resp. restart your browser the myDM instance's Webclient should launch properly again.
The Webclient needs to be fixed. It should be more robust about invalid cookies.
See also ticket:994#comment:12
BTW: The same error occured to me when i once turned the "DeepaMehta" workspace into a "Confidential" one. After that and ente oing dm4-webclient to the "front door" it could not initialize itself properly (so that i could login even if i wanted) and that was due to the same error message (but because the "load all topic types" call failed, since core types were suddenly not readable).