Bug 439841 - CDO Security manager failling in MEMStore configuration
Summary: CDO Security manager failling in MEMStore configuration
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-17 16:04 EDT by Laurent Le Moux CLA
Modified: 2020-12-11 10:43 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent Le Moux CLA 2014-07-17 16:04:00 EDT
Hi all,

I've been using Eclipse Modeling Luna M6 since March with the corresponding integration release of CDO 4.3 at that time.

The security manager used to work just fine with a MEMStore configuration or a DBStore one (H2 based).

Since I recently downloaded Luna official release including CDO 4.3 distribution, MEMStore configuration fails to load the security resource with an invalid 'cdo://repo1/security' URI exception a couple of seconds after starting up the CDO server.

Whereas it is still working fine with a DBStore configuration.

I experienced that using the CDO explorer I can connect as Administrator. I can see the security resource content but I can not commit any modification in MEMStore when I still can do it in DBStore context.

I also noticed that, in the MEMStore configuration, the /home and /home/Administrator directories are missing.
And I suspect it could be the result of getting the above exception at server start up...

Kind regards,

Laurent Le Moux
Comment 1 Eike Stepper CLA 2015-07-14 02:13:58 EDT
Moving all open bugzillas to 4.5.
Comment 2 Eike Stepper CLA 2016-07-31 00:56:59 EDT
Moving all unaddressed bugzillas to 4.6.
Comment 3 Eike Stepper CLA 2017-12-28 01:15:56 EST
Moving all open bugs to 4.7
Comment 4 Eike Stepper CLA 2019-11-08 02:07:46 EST
Moving all unresolved issues to version 4.8-
Comment 5 Eike Stepper CLA 2019-12-13 12:48:21 EST
Moving all unresolved issues to version 4.9
Comment 6 Eike Stepper CLA 2020-12-11 10:43:02 EST
Moving to 4.13.