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-889: Can't set a SecurityContextHolderStrategy instance for SecurityContextHolder directly #1144

Closed
spring-projects-issues opened this issue Jun 17, 2008 · 3 comments
Labels
in: core An issue in spring-security-core 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
Milestone

Comments

@spring-projects-issues
Copy link

Jürgen Heil(Migrated from SEC-889) said:

Currently i can put a custom strategy to hold the SecurityContext via SecurityContextHolder.setStrategyName(String). By SecurityContextHolder.initialize() the class try to load the custom strategy. When the custom class isn’t in the classpath i get a ClassNotFoundException. I found no way to set the instance directly.

@spring-projects-issues
Copy link
Author

Luke Taylor said:

I’m not quite clear what the problem is? Could you expand a bit on your requirements?

For example, why would your custom class not be on the classpath?

@spring-projects-issues
Copy link
Author

Jürgen Heil said:

My class ist not in the classpath because i’m using an OSGi-Container. I solved it by implementing a fragment bundle to your security-bundle.

@spring-projects-issues
Copy link
Author

Luke Taylor said:

OK - that sounds like a suitable resolution so I'll close as "won't fix". If there are any other comments or suggestions, please enter them here.

@spring-projects-issues spring-projects-issues added in: core An issue in spring-security-core Closed type: enhancement A general enhancement status: declined A suggestion or change that we don't feel we should currently apply type: jira An issue that was migrated from JIRA labels Feb 5, 2016
@spring-projects-issues spring-projects-issues added this to the 3.0.0 M1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core An issue in spring-security-core 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

1 participant