Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Configuration of BasicLookupStrategy for Access Control Lists

 
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am looking at an example of Spring Security ACLs. The project uses the following file to configure ACL, my question is on the second and third beans (id = adminRole, and lookupStrategy):


The adminRole bean is created with the constructor argument of "admin". The project description indicates this is a special authority that sits outside the ACLs determining who can change the ACLs. It states that a system-wide administrative authority should be used which is what is being passed in here by "admin". Is the value "admin" recognized by Spring security (I could not find it in the Spring Security code or documentation)? The project has ROLE_ADMIN defined in its database tables, but I don't see anything mapping this value of "admin" to ROLE_ADMIN in the database. Thanks in advance.


 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic