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

Allow jakarta.security.jacc.PolicyConfigurationFactory.provider as context parameter #151

Open
arjantijms opened this issue Mar 21, 2024 · 0 comments
Assignees
Milestone

Comments

@arjantijms
Copy link
Contributor

The system property with name "jakarta.security.jacc.PolicyConfigurationFactory.provider" is used to set an alternative PolicyConfigurationFactory in Jakarta Authorization. This parameter is however not always easy to set (depending on how much the runtime is under the control of the deployer) and its basically undefined where exactly the class that the property references should live.

On the (archived) mailing list we discussed at the time alternatives to this, and suggested to use a deployable artefact for this. At the time a RAR was proposed, but since then the emphasis has shifted away from RAR and JAR deployments, to mostly WARs.

As such we can introduce a web.xml context parameter that is treated the same as the system property, but takes precedence, and loads the PolicyConfigurationFactory using the web archive's class loader.

@arjantijms arjantijms added this to the 3.0 milestone Mar 21, 2024
@arjantijms arjantijms self-assigned this Mar 21, 2024
arjantijms added a commit to arjantijms/authorization that referenced this issue Mar 24, 2024
…e#151

This makes sure the platform or authorization implementation can obtain
the PolicyConfigurationFactory

Signed-off-by: Arjan Tijms <arjan.tijms@omnifish.ee>
arjantijms added a commit that referenced this issue Mar 24, 2024
Allow the PolicyConfigurationFactory to be set in support of #151
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant