json - Spring security 4. Architect structure for user management page -


spring security uses userdetailsmanager manage users & authorities. want use same implementation jdbcuserdetailsmanager manage user page admin (user crud, managing groups, pagination). unfortunately there no implementation paging, manage groups , on.

so i've got issues:

  1. user crud because of json convertation rest.
  2. group crud because of json convertation rest.
  3. user paging because of userdetailsmanager has no correspond implementation.
  4. group paging - no implementation.
  5. user json pojo (for create\update operations used userdetails has implementations inetorgperson, person, user but... i've got json convertation issue, can not mark classes @jsonignore).
  6. user pojo json (for read operation can not remove data important fields (for example: password)).

all of issues have few solution ways:

  1. 1.1. create 1 more user object similar user, add expected json annotations or in rest controller create builder build user object input parameter map (builder pattern think ugly way manage if implemented once) 1.2. add spring-datajpa repository (duplicates security part of jdbcuserdetailsmanager) or extend jdbcuserdetailsmanager , add unimplemented part manage users, groups...
  2. solution same 1.
  3. if 1. implemeted using spring-data-jpa - no problems, other case needs implement correspond factory builders provide paging in dynamic way.
  4. solution same 3.
  5. solved on 1., 2. steps.
  6. solved on 1., 2. steps.

which solution way should follow (implement managers spring-data-jpa based additional pojos or expand functionality jdbcuserdetailsmanager) ?

describing situation, think i'll implement solution using spring-data-jpa , pojo-entities have crud , json manipulating abilities. way seems better saving implementation time, , code more cleaner support generation.

if mistook in choice, let me know please. please let me know if issues solved in spring (sorry did not find solutions described issues). believe wants other solution architecture - discuss or consider clever ideas.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more