Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEC-1780: Drop in JPA based replacement for the JDBC ACL Security Implementation #2015

Closed
spring-projects-issues opened this issue Jul 8, 2011 · 1 comment
Assignees
Labels
in: acl An issue in spring-security-acl status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement type: jira An issue that was migrated from JIRA

Comments

@spring-projects-issues
Copy link

spring-projects-issues commented Jul 8, 2011

Claude Warren (Migrated from SEC-1780) said:

I have implemented a drop in JPA based replacement for the JDBC ACL security implementation.

We had an issue where we wanted to create ACL entries and and use them within a JPA bean test. The issue we found was that the JDBC ACL implementation used a different session so we were not able to create the ACLs, use them, and roll them back in a single transaction. This implementation allows that.

The attached jar contains the SOURCE for the implementation. It does not modify any existing classes but creates jpa packages equivalent to the existing jdbc packages.

Test cases are included

The jpa-security.xml provides an example of the configuration. It does require an externally defined userDetailsService bean.

The design utilizes the JPA transactions to isolate changes until a commit occurs. The design also utilizes the DB functionality to store large ACLs.

The SQL code has been tested on MySQL.

@spring-projects-issues spring-projects-issues added in: acl An issue in spring-security-acl Open type: enhancement A general enhancement type: jira An issue that was migrated from JIRA labels Feb 5, 2016
@rwinch rwinch removed the Open label May 3, 2019
@rwinch
Copy link
Member

rwinch commented May 25, 2021

Thank you for the report. We have no plans to support a JPA based implementation of our interfaces. It is easy enough for those that want to use JPA to write their own implementation of the interface.

@rwinch rwinch closed this as completed May 25, 2021
@rwinch rwinch self-assigned this May 25, 2021
@rwinch rwinch added the status: declined A suggestion or change that we don't feel we should currently apply label May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: acl An issue in spring-security-acl status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement type: jira An issue that was migrated from JIRA
Projects
None yet
Development

No branches or pull requests

2 participants