You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Joze Rihtarsic (Jira)" <ji...@apache.org> on 2024/05/24 15:06:00 UTC
[jira] [Updated] (SANTUARIO-621) Syncrhonization of the xmlsec configuration
[ https://issues.apache.org/jira/browse/SANTUARIO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joze Rihtarsic updated SANTUARIO-621:
-------------------------------------
Description:
In the current version of the XMLSEC library, there are two distinct configuration classes:
# Generic Configuration ((Class: {*}org.apache.xml.security.Init{*}):
*
** This class provides a set of default values, which are hardcoded.
** Users have the option to override these defaults by specifying a classpath resource defined in system property
*org.apache.xml.security.resource.config*
** the file must be in classpath at init time and it can not be overridden
# STAX Configuration (Class: {*}org.apache.xml.security.stax.config.Init{*}):
*
** The STAX configuration class utilizes an XML resource named /security-config.xml.
** The Initialization is triggered by static block in
{color:#000000}XMLSec.java class{color}
*
** However, it is possible to reinitialize the settings by invoking org.apache.xml.security.stax.config.Init.init with a new resource.
Differences Between Generic-Init and STAX-Init Configurations:
# XML Namespace Expectations:
*
** The generic configuration expects the namespace: *[http://www.xmlsecurity.org/NS/#configuration.*]
** The STAX configuration, on the other hand, expects the namespace {*}[http://www.xmlsecurity.org/NS/configuration]{*}.
# Language Definition in XML:
*
** For the generic configuration, the scheme expects an element with the following attributes:
{code:java}
<ResourceBundles defaultLanguageCode="en" defaultCountryCode="US" />{code}
** In contrast, the STAX configuration relies on XML properties:
{code:java}
<Property NAME="DefaultLanguageCode" VAL="en" />
<Property NAME="DefaultCountryCode" VAL="US" /> {code}
# Parsing of the Init XML Configuration:
*
** The generic configuration (Generic-Init) uses the DOM (Document Object Model) with a custom implementation for element and attribute detection.
** The STAX configuration (Stax-Init) employs JAXB (Java Architecture for XML Binding) with a well-defined schema provided as a resource {*}(/scheme/security-config.xsd{*}).
The task aims to enhance transparency and clarity in configuration synchronization.
The scope of the task is to debate and define XMLSEC configuration more precisely, identify the configuration in use, outline a scheme for custom configuration, and explain how users can update the default settings. And add list of outdated algorithms.
Suggestion to implement.
Define only one Init/Configuration class having best options from both approaches:
The class will be this:
{*}org.apache.xml.security.Init{*}{*}{*}
The configuration is based XML and provided scheme (from STAX), which will be also used to validate the XML .
For de-serializing properties is used JAXB framework.
For overriding the configuration users will have the option to override the defaults by specifying a classpath resource defined with system property
*org.apache.xml.security.resource.config*
was:
In the current version of the XMLSEC library, there are two distinct configuration classes:
# Generic Configuration ((Class: {*}org.apache.xml.security.Init{*}):
** This class provides a set of default values, which are hardcoded.
** Users have the option to override these defaults by specifying a classpath resource defined in system property
*org.apache.xml.security.resource.config*
# STAX Configuration (Class: {*}org.apache.xml.security.stax.config.Init{*}):
** The STAX configuration class utilizes an XML resource named /security-config.xml.
** The Initialization is triggered by static block in
{color:#000000}XMLSec.java class{color}
** However, it is possible to reinitialize the settings by invoking org.apache.xml.security.stax.config.Init.init with a new resource.
Differences Between Generic-Init and STAX-Init Configurations:
# XML Namespace Expectations:
** The generic configuration expects the namespace: *http://www.xmlsecurity.org/NS/#configuration.*
** The STAX configuration, on the other hand, expects the namespace {*}http://www.xmlsecurity.org/NS/configuration{*}.
# Language Definition in XML:
** For the generic configuration, the scheme expects an element with the following attributes:
{code:java}
<ResourceBundles defaultLanguageCode="en" defaultCountryCode="US" />{code}
** In contrast, the STAX configuration relies on XML properties:
{code:java}
<Property NAME="DefaultLanguageCode" VAL="en" />
<Property NAME="DefaultCountryCode" VAL="US" /> {code}
# Parsing of the Init XML Configuration:
** The generic configuration (Generic-Init) uses the DOM (Document Object Model) with a custom implementation for element and attribute detection.
** The STAX configuration (Stax-Init) employs JAXB (Java Architecture for XML Binding) with a well-defined schema provided as a resource {*}(/scheme/security-config.xsd{*}).
The task aims to enhance transparency and clarity in configuration synchronization.
The scope of the task is to debate and define XMLSEC configuration more precisely, identify the configuration in use, outline a scheme for custom configuration, and explain how users can update the default settings. And add list of outdated algorithms.
> Syncrhonization of the xmlsec configuration
> -------------------------------------------
>
> Key: SANTUARIO-621
> URL: https://issues.apache.org/jira/browse/SANTUARIO-621
> Project: Santuario
> Issue Type: Improvement
> Reporter: Joze Rihtarsic
> Assignee: Colm O hEigeartaigh
> Priority: Major
>
> In the current version of the XMLSEC library, there are two distinct configuration classes:
> # Generic Configuration ((Class: {*}org.apache.xml.security.Init{*}):
> *
> ** This class provides a set of default values, which are hardcoded.
> ** Users have the option to override these defaults by specifying a classpath resource defined in system property
> *org.apache.xml.security.resource.config*
> ** the file must be in classpath at init time and it can not be overridden
>
> # STAX Configuration (Class: {*}org.apache.xml.security.stax.config.Init{*}):
> *
> ** The STAX configuration class utilizes an XML resource named /security-config.xml.
> ** The Initialization is triggered by static block in
> {color:#000000}XMLSec.java class{color}
> *
> ** However, it is possible to reinitialize the settings by invoking org.apache.xml.security.stax.config.Init.init with a new resource.
> Differences Between Generic-Init and STAX-Init Configurations:
> # XML Namespace Expectations:
> *
> ** The generic configuration expects the namespace: *[http://www.xmlsecurity.org/NS/#configuration.*]
> ** The STAX configuration, on the other hand, expects the namespace {*}[http://www.xmlsecurity.org/NS/configuration]{*}.
> # Language Definition in XML:
> *
> ** For the generic configuration, the scheme expects an element with the following attributes:
> {code:java}
> <ResourceBundles defaultLanguageCode="en" defaultCountryCode="US" />{code}
>
> ** In contrast, the STAX configuration relies on XML properties:
> {code:java}
> <Property NAME="DefaultLanguageCode" VAL="en" />
> <Property NAME="DefaultCountryCode" VAL="US" /> {code}
>
> # Parsing of the Init XML Configuration:
> *
> ** The generic configuration (Generic-Init) uses the DOM (Document Object Model) with a custom implementation for element and attribute detection.
> ** The STAX configuration (Stax-Init) employs JAXB (Java Architecture for XML Binding) with a well-defined schema provided as a resource {*}(/scheme/security-config.xsd{*}).
> The task aims to enhance transparency and clarity in configuration synchronization.
> The scope of the task is to debate and define XMLSEC configuration more precisely, identify the configuration in use, outline a scheme for custom configuration, and explain how users can update the default settings. And add list of outdated algorithms.
> Suggestion to implement.
> Define only one Init/Configuration class having best options from both approaches:
> The class will be this:
> {*}org.apache.xml.security.Init{*}{*}{*}
> The configuration is based XML and provided scheme (from STAX), which will be also used to validate the XML .
> For de-serializing properties is used JAXB framework.
> For overriding the configuration users will have the option to override the defaults by specifying a classpath resource defined with system property
> *org.apache.xml.security.resource.config*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)