Using interface instead of generic user

Letractively / acris

Automatically exported from code.google.com/p/acris

0 stars 0 forks source link

Using interface instead of generic user #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Security should work only with UserDetail or another interface instead of 
concrete implementation of user (GenericUser)

Original issue reported on code.google.com by nejakyus...@gmail.com on 14 Jul 2010 at 3:53

GoogleCodeExporter commented 8 years ago

Original comment by ladislav...@gmail.com on 14 Jul 2010 at 9:32

Added labels: security

GoogleCodeExporter commented 8 years ago

Original comment by nejakyus...@gmail.com on 23 Jul 2010 at 6:59

GoogleCodeExporter commented 8 years ago

- Remove hibernate annotations from SecurityRole (from client package, 
hibernate related things should be only on the server side code)
- Remove ILightEntity, LightEntity from domain objects - create 
acris-security-gilead project with gilead related classes (clear entities 
should be in acris-security, extended entities with ILightEntity implementation 
should be in a new a project)
- Move security related exporters also there (think about the refactoring of 
them - if possible)

Original comment by nejakyus...@gmail.com on 20 Aug 2010 at 8:13

GoogleCodeExporter commented 8 years ago

starting with dividing the stuff into 2 separate projects acris-security & 
acris-security-gilead

Original comment by nejakyus...@gmail.com on 20 Aug 2010 at 8:17

Changed state: Started

GoogleCodeExporter commented 8 years ago

Original comment by ladislav...@gmail.com on 21 Aug 2010 at 9:11

Added labels: Security
Removed labels: security

GoogleCodeExporter commented 8 years ago

Original comment by nejakyus...@gmail.com on 25 Aug 2010 at 4:57

Added labels: Milestone-1.0.1

GoogleCodeExporter commented 8 years ago

Original comment by nejakyus...@gmail.com on 22 Sep 2010 at 12:12

Changed state: Fixed