[JBoss JIRA] (WFLY-8498) JSTL TransformSupport XSL import not finding relative path
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8498?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-8498:
------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1320747, https://bz.apache.org/bugzilla/show_bug.cgi?id=60950 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1320747)
> JSTL TransformSupport XSL import not finding relative path
> ----------------------------------------------------------
>
> Key: WFLY-8498
> URL: https://issues.jboss.org/browse/WFLY-8498
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 11.0.0.Alpha1
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Priority: Blocker
> Labels: eap71_beta
> Attachments: test2.war
>
>
> Regression compared to WildFly 10.0.0.Final
> For more details see: https://bugzilla.redhat.com/show_bug.cgi?id=1320747
> Expected browser output:
> {code}
> Books Info:
> The Hobbit J. R. R. Tolkien 100
> The Man in the High Castle Philip K. Dick 200
> {code}
> Actual browser output:
> {code}
> Error processing request
> Context Path:
> /test2
> Servlet Path:
> /test3.jsp
> Path Info:
> null
> Query String:
> null
> Stack Trace
> javax.servlet.ServletException: javax.servlet.jsp.JspTagException: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Had IO Exception with stylesheet file: parent.xsl javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: parent.xsl
> org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:886)
> org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:818)
> org.apache.jsp.test3_jsp._jspService(test3_jsp.java:146)
> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433)
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:402)
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:346)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
> io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> io.undertow.jsp.JspFileHandler.handleRequest(JspFileHandler.java:32)
> io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:46)
> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> io.undertow.server.Connectors.executeRootHandler(Connectors.java:211)
> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809)
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> java.lang.Thread.run(Thread.java:745)
> {code}
> Server log:
> {code}
> 2017-03-01 14:10:22,475 ERROR [io.undertow.request] (default task-3) UT005023: Exception handling request to /test2/test3.jsp: javax.servlet.ServletException: javax.servlet.jsp.JspTagException: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Had IO Exception with stylesheet file: parent.xsl
> javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: parent.xsl
> at org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:886)
> at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:818)
> at org.apache.jsp.test3_jsp._jspService(test3_jsp.java:146)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:402)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:346)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.jsp.JspFileHandler.handleRequest(JspFileHandler.java:32)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:46)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1700)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:211)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Had IO Exception with stylesheet file: parent.xsl
> javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: parent.xsl
> at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:942)
> at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:780)
> at __redirected.__TransformerFactory.newTransformer(__TransformerFactory.java:133)
> at org.apache.taglibs.standard.util.XmlUtil.newTransformer(XmlUtil.java:187)
> at org.apache.taglibs.standard.tag.common.xml.TransformSupport.doStartTag(TransformSupport.java:124)
> at org.apache.jsp.test3_jsp._jspx_meth_x_005ftransform_005f0(test3_jsp.java:275)
> at org.apache.jsp.test3_jsp._jspService(test3_jsp.java:129)
> ... 45 more
> Caused by: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Had IO Exception with stylesheet file: parent.xsl
> javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: parent.xsl
> at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:934)
> ... 51 more
> Caused by: org.xml.sax.SAXException: Had IO Exception with stylesheet file: parent.xsl
> javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: parent.xsl
> at org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:922)
> at org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:950)
> at org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:322)
> at org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclude.java:158)
> at org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.java:626)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:498)
> at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:180)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:275)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1653)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324)
> at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:875)
> at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:798)
> at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:108)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1198)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:564)
> at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:926)
> ... 51 more
> Caused by: javax.xml.transform.TransformerException: Had IO Exception with stylesheet file: parent.xsl
> at org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:907)
> ... 66 more
> Caused by: java.net.MalformedURLException: unknown protocol: jstl
> at java.net.URL.<init>(URL.java:600)
> at java.net.URL.<init>(URL.java:490)
> at java.net.URL.<init>(URL.java:439)
> at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:964)
> at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:144)
> at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:832)
> at org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:798)
> at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:108)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1198)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:564)
> at org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:312)
> ... 64 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1506) drools-docs improvements: file structure, dead images, etc
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1506?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1506:
-------------------------------------
Description:
See latest docs here from jenkins:
https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/kie-docs/lastSucc...
- 4 mentions of KnowledgeSession should be replaced by KieSession. Same for KnowledgeBase, etc.
Do a find in single_html output for regex "Knowledge\w".
- Chapter 3 Compatibility matrix is 4 lines, should be a nested section in another chapter
- Dead images.
- Dead sections?
- Images in differently named directory than their section adoc.
For example: images in directory GettingInvolved in shared-kie-docs
- Release notes should not reuse images from rest of docs,
because those images get updated over time
and release notes should not change retroactively automatically.
Copy-paste those images in the release notes directories to reuse them.
- Every section header needs an anchorId.
was:
- 4 mentions of KnowledgeSession should be replaced by KieSession. Same for KnowledgeBase, etc.
Do a find in single_html output for regex "Knowledge\w".
- Chapter 3 Compatibility matrix is 4 lines, should be a nested section in another chapter
- Dead images.
- Dead sections?
- Images in differently named directory than their section adoc.
For example: images in directory GettingInvolved in shared-kie-docs
- Release notes should not reuse images from rest of docs,
because those images get updated over time
and release notes should not change retroactively automatically.
Copy-paste those images in the release notes directories to reuse them.
- Every section header needs an anchorId.
> drools-docs improvements: file structure, dead images, etc
> ----------------------------------------------------------
>
> Key: DROOLS-1506
> URL: https://issues.jboss.org/browse/DROOLS-1506
> Project: Drools
> Issue Type: Task
> Components: docs
> Affects Versions: 7.0.0.Beta8
> Reporter: Geoffrey De Smet
> Assignee: Edson Tirelli
>
> See latest docs here from jenkins:
> https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/kie-docs/lastSucc...
> - 4 mentions of KnowledgeSession should be replaced by KieSession. Same for KnowledgeBase, etc.
> Do a find in single_html output for regex "Knowledge\w".
> - Chapter 3 Compatibility matrix is 4 lines, should be a nested section in another chapter
> - Dead images.
> - Dead sections?
> - Images in differently named directory than their section adoc.
> For example: images in directory GettingInvolved in shared-kie-docs
> - Release notes should not reuse images from rest of docs,
> because those images get updated over time
> and release notes should not change retroactively automatically.
> Copy-paste those images in the release notes directories to reuse them.
> - Every section header needs an anchorId.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1506) drools-docs improvements: file structure, dead images, etc
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1506:
----------------------------------------
Summary: drools-docs improvements: file structure, dead images, etc
Key: DROOLS-1506
URL: https://issues.jboss.org/browse/DROOLS-1506
Project: Drools
Issue Type: Task
Components: docs
Affects Versions: 7.0.0.Beta8
Reporter: Geoffrey De Smet
Assignee: Edson Tirelli
- 4 mentions of KnowledgeSession should be replaced by KieSession. Same for KnowledgeBase, etc.
Do a find in single_html output for regex "Knowledge\w".
- Chapter 3 Compatibility matrix is 4 lines, should be a nested section in another chapter
- Dead images.
- Dead sections?
- Images in differently named directory than their section adoc.
For example: images in directory GettingInvolved in shared-kie-docs
- Release notes should not reuse images from rest of docs,
because those images get updated over time
and release notes should not change retroactively automatically.
Copy-paste those images in the release notes directories to reuse them.
- Every section header needs an anchorId.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8496) Unclear model description of core-pool-size attribute in IO subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8496?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-8496:
----------------------------------------
[~rpelisse] Please move this to WFCORE and update the commit message and PR description. Thanks.
> Unclear model description of core-pool-size attribute in IO subsystem
> ---------------------------------------------------------------------
>
> Key: WFLY-8496
> URL: https://issues.jboss.org/browse/WFLY-8496
> Project: WildFly
> Issue Type: Bug
> Components: IO
> Affects Versions: 11.0.0.Alpha1
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Minor
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> */subsystem=io/worker=*:read-attribute(name=core-pool-size)*
> Current model description: "Core worker thread pool size"
> Suggested improvement: "Minimum number of threads to keep in the underlying java.util.concurrent.ThreadPoolExecutor even if they are idle. Threads over this limit will be terminated over time specified by task-keepalive attribute."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2387) Elytron subsystem requires user to input OIDs
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2387?page=com.atlassian.jira.plugi... ]
Jan Kalina resolved WFCORE-2387.
--------------------------------
Fix Version/s: 3.0.0.Beta11
Assignee: Jan Kalina
Resolution: Done
> Elytron subsystem requires user to input OIDs
> ---------------------------------------------
>
> Key: WFCORE-2387
> URL: https://issues.jboss.org/browse/WFCORE-2387
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Labels: user_experience
> Fix For: 3.0.0.Beta11
>
>
> On couple of places in elytron subsystem raw oids are expected from user input, e.g. {{2.5.4.4}} . Is there chance some aliasing could be introduced? So for example human readable {{surname}} can be used?
> * kerberos-security-factory
> ** mechanism-oids
> * x500-principal-decoder
> ** oid
> ** required-oids
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2387) Elytron subsystem requires user to input OIDs
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2387?page=com.atlassian.jira.plugi... ]
Jan Kalina commented on WFCORE-2387:
------------------------------------
Resolved for:
* kerberos-security-factory in WFCORE-2409
* x500-principal-decoder in WFLY-7176
> Elytron subsystem requires user to input OIDs
> ---------------------------------------------
>
> Key: WFCORE-2387
> URL: https://issues.jboss.org/browse/WFCORE-2387
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Martin Choma
> Labels: user_experience
>
> On couple of places in elytron subsystem raw oids are expected from user input, e.g. {{2.5.4.4}} . Is there chance some aliasing could be introduced? So for example human readable {{surname}} can be used?
> * kerberos-security-factory
> ** mechanism-oids
> * x500-principal-decoder
> ** oid
> ** required-oids
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2615) Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2615?page=com.atlassian.jira.plugi... ]
David Lloyd commented on WFCORE-2615:
-------------------------------------
The current definition of allow-sasl-mechanisms is to include a mechanism even if the configuration would otherwise not suggest that the mechanism is possible. The current definition of forbid-sasl-mechanisms is to prevent a mechanism from being used, even if the configuration would suggest that it is possible.
There is presently no mechanism "whitelist" function. If we introduce such a thing, it should be called "limit-sasl-mechanism-set" or something like that. So I consider this "Not a bug".
> Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-2615
> URL: https://issues.jboss.org/browse/WFCORE-2615
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta10
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
> Attachments: dep.war, wireshark.pcapng
>
>
> In case when attribute allow-sasl-mechanisms from Elytron Authentication Configuration includes some SASL mechanisms then this attribute (and mechanisms configured there) is not taken into account during choosing SASL mechanism. It means that client tries to use all of mechanisms allowed on server side even if client does not allow them. e.g. in case when server side allowed DIGEST-MD5 and JBOSS-LOCAL-USER and client side allows PLAIN, then it tries to use DIGEST-MD5 and JBOSS-LOCAL-USER mechanisms.
> See log from wireshark in attachments. This is log for server configured through "Steps to Reproduce".
> This happens also for using allow-sasl-mechanisms from wildfly config and also for programatically configured client.
> We request blocker since it allows to use some SASL mechanisms even if they are not allowed on client side.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months