[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-7194:
-----------------------------------
I may be misremembering, but I _think_ we can use the default algorithm but I believe that in turn would make a key store configuration useless if it is indeed used. By defining a key store I think we effectively establish our own key manager. [~dlofthouse] should know for sure I think...
> Simplify creation of trust/key-manager in elytron
> -------------------------------------------------
>
> Key: WFLY-7194
> URL: https://issues.jboss.org/browse/WFLY-7194
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> If I want to setup TLS [1], I have to create key manager with CLI command
> {code}
> /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509")
> {code}
> 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used.
> 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone.
> 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required.
> {code}
> <xs:attribute name="key-store" type="xs:string" use="optional">
> <xs:annotation>
> <xs:documentation>
> Reference to the KeyStore to use with the KeyManager.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> {code}
> 4.{{password}} attribute is optional, probably should be required
> {code}
> "password" => {
> "type" => STRING,
> "description" => "The password to use when initialising the underlying KeyManagerFactory.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "1.0.0",
> "reason" => "Will be updated to use proper CredentialStore references."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {code}
> [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7284) group-properties can be added without path in Elytron properties-realm which results to invalid server configuration
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7284?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev resolved WFLY-7284.
---------------------------------
Fix Version/s: 11.0.0.Alpha1
Resolution: Done
> group-properties can be added without path in Elytron properties-realm which results to invalid server configuration
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7284
> URL: https://issues.jboss.org/browse/WFLY-7284
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Ilia Vassilev
> Fix For: 11.0.0.Alpha1
>
>
> Adding {{groups-properties}} without {{path}} through CLI is allowed by Elytron subsystem which results to XMLStreamException after server is reloaded/restarted.
> Exception in server log after reload/restart:
> {code}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.server.ServerService.boot(ServerService.java:355)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[345,21]
> Message: WFLYCTL0133: Missing required attribute(s): path
> at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:180)
> at org.wildfly.extension.elytron.RealmParser.readFileAttributes(RealmParser.java:522)
> at org.wildfly.extension.elytron.RealmParser.readPropertiesRealm(RealmParser.java:337)
> at org.wildfly.extension.elytron.RealmParser.readRealms(RealmParser.java:118)
> at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:114)
> at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:72)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> at org.jboss.as.server.parsing.StandaloneXml_5.parseServerProfile(StandaloneXml_5.java:591)
> at org.jboss.as.server.parsing.StandaloneXml_5.readServerElement(StandaloneXml_5.java:245)
> at org.jboss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:144)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> ... 3 more
> FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7284) group-properties can be added without path in Elytron properties-realm which results to invalid server configuration
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7284?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev edited comment on WFLY-7284 at 11/1/16 10:00 AM:
---------------------------------------------------------------
This issue is resolved with the PR [1] submitted for WFLY-7172 which is fixed in Elytron Subsystem 1.0.0.Alpha12.
[1] https://github.com/wildfly-security/elytron-subsystem/pull/251
was (Author: ivassile):
This issue is resolved with the PR [1] submitted for WFLY-7172.
[1] https://github.com/wildfly-security/elytron-subsystem/pull/251
> group-properties can be added without path in Elytron properties-realm which results to invalid server configuration
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7284
> URL: https://issues.jboss.org/browse/WFLY-7284
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Ilia Vassilev
>
> Adding {{groups-properties}} without {{path}} through CLI is allowed by Elytron subsystem which results to XMLStreamException after server is reloaded/restarted.
> Exception in server log after reload/restart:
> {code}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.server.ServerService.boot(ServerService.java:355)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[345,21]
> Message: WFLYCTL0133: Missing required attribute(s): path
> at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:180)
> at org.wildfly.extension.elytron.RealmParser.readFileAttributes(RealmParser.java:522)
> at org.wildfly.extension.elytron.RealmParser.readPropertiesRealm(RealmParser.java:337)
> at org.wildfly.extension.elytron.RealmParser.readRealms(RealmParser.java:118)
> at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:114)
> at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:72)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> at org.jboss.as.server.parsing.StandaloneXml_5.parseServerProfile(StandaloneXml_5.java:591)
> at org.jboss.as.server.parsing.StandaloneXml_5.readServerElement(StandaloneXml_5.java:245)
> at org.jboss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:144)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> ... 3 more
> FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7284) group-properties can be added without path in Elytron properties-realm which results to invalid server configuration
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7284?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev commented on WFLY-7284:
-------------------------------------
This issue is resolved with the PR [1] submitted for WFLY-7172.
[1] https://github.com/wildfly-security/elytron-subsystem/pull/251
> group-properties can be added without path in Elytron properties-realm which results to invalid server configuration
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7284
> URL: https://issues.jboss.org/browse/WFLY-7284
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Ilia Vassilev
>
> Adding {{groups-properties}} without {{path}} through CLI is allowed by Elytron subsystem which results to XMLStreamException after server is reloaded/restarted.
> Exception in server log after reload/restart:
> {code}
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> at org.jboss.as.server.ServerService.boot(ServerService.java:355)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:302)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[345,21]
> Message: WFLYCTL0133: Missing required attribute(s): path
> at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:180)
> at org.wildfly.extension.elytron.RealmParser.readFileAttributes(RealmParser.java:522)
> at org.wildfly.extension.elytron.RealmParser.readPropertiesRealm(RealmParser.java:337)
> at org.wildfly.extension.elytron.RealmParser.readRealms(RealmParser.java:118)
> at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:114)
> at org.wildfly.extension.elytron.ElytronSubsystemParser.readElement(ElytronSubsystemParser.java:72)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> at org.jboss.as.server.parsing.StandaloneXml_5.parseServerProfile(StandaloneXml_5.java:591)
> at org.jboss.as.server.parsing.StandaloneXml_5.readServerElement(StandaloneXml_5.java:245)
> at org.jboss.as.server.parsing.StandaloneXml_5.readElement(StandaloneXml_5.java:144)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107)
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> ... 3 more
> FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1912:
------------------------------------------
Playing with this it works fine.
Start the server:
{code}
[disconnected /] embed-server --std-out=echo --admin-only=false -c=standalone-full.xml
...
{code}
Deploy an app missing a queue dependency, but ensure the failure doesn't trigger rollback:
{code}
[standalone@embedded /] deploy ~/tmp/luckywinner.ear --unmanaged --headers={rollback-on-runtime-failure=false}
...
08:21:25,416 INFO [org.jboss.as.ejb3] (MSC service thread 2-6) WFLYEJB0042: Started message driven bean 'LuckyWinnerMDB' with 'activemq-ra.rar' resource adapter
08:21:25,472 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 7) WFLYCTL0013: Operation ("deploy") failed - address: ({"deployment" => "luckywinner.ear"}) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.queue.demo"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.luckywinner.luckywinner.env.\"org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet\".queue is missing [jboss.naming.context.java.queue.demo]"]
}
08:21:25,492 INFO [org.jboss.as.server] (AeshProcess: 7) WFLYSRV0010: Deployed "luckywinner.ear" (runtime-name : "luckywinner.ear")
08:21:25,493 INFO [org.jboss.as.controller] (AeshProcess: 7) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.naming.context.java.queue.demo (missing) dependents: [service jboss.naming.context.java.module.luckywinner.luckywinner.env."org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet".queue]
...
{code}
Add the missing queue:
{code}
[standalone@embedded /] jms-queue add --queue-address=DemoQueue --entries=queue/demo
08:22:17,427 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: Deploying queue jms.queue.DemoQueue
08:22:17,611 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 72) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/luckywinner'
08:22:18,047 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151002: Reconnected with broker
08:22:18,114 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/luckywinner' for server 'default-server'
08:22:18,191 INFO [org.jboss.as.controller] (AeshProcess: 8) WFLYCTL0183: Service status report
WFLYCTL0185: Newly corrected services:
service jboss.naming.context.java.queue.demo (new available)
{code}
App now works.
Remove the queue from the config. Suppress the failure.
{code}
[standalone@embedded /] jms-queue remove --queue-address=DemoQueue --headers={rollback-on-runtime-failure=false}
08:23:32,344 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0022: Unregistered web context: '/luckywinner' from server 'default-server'
08:23:32,426 INFO [org.jboss.as.controller] (AeshProcess: 9) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.naming.context.java.queue.demo (missing) dependents: [service jboss.naming.context.java.module.luckywinner.luckywinner.env."org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet".queue]
WFLYCTL0171: Removing services has lead to unsatisfied dependencies:
Service jboss.naming.context.java.queue.demo was depended upon by service jboss.naming.context.java.module.luckywinner.luckywinner.env."org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet".queue
{code}
Reload to the now broken config. Deployment fails but is not rolled back:
{code}
[standalone@embedded /] reload --admin-only=false
08:23:48,743 INFO [org.jboss.as.ejb3] (MSC service thread 2-7) WFLYEJB0042: Started message driven bean 'LuckyWinnerMDB' with 'activemq-ra.rar' resource adapter
08:23:48,748 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "luckywinner.ear")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.queue.demo"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.luckywinner.luckywinner.env.\"org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet\".queue is missing [jboss.naming.context.java.queue.demo]"]
}
08:23:48,753 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "luckywinner.ear" (runtime-name : "luckywinner.ear")
08:23:48,754 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.naming.context.java.queue.demo (missing) dependents: [service jboss.naming.context.java.module.luckywinner.luckywinner.env."org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet".queue]
08:23:48,768 INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation java:/queue/demo
08:23:48,805 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
08:23:48,805 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
08:23:48,805 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 11.0.0.Alpha1-SNAPSHOT (WildFly Core 3.0.0.Alpha10) started (with errors) in 520ms - Started 566 of 833 services (11 services failed or missing dependencies, 468 services are lazy, passive or on-demand)
{code}
Fix the missing queue:
{code}
[standalone@embedded /] jms-queue add --queue-address=DemoQueue --entries=queue/demo
08:23:57,240 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 9) AMQ221003: Deploying queue jms.queue.DemoQueue
08:23:57,259 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 18) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/luckywinner'
08:23:57,370 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 18) WFLYUT0021: Registered web context: '/luckywinner' for server 'default-server'
08:23:57,413 INFO [org.jboss.as.controller] (AeshProcess: 11) WFLYCTL0183: Service status report
WFLYCTL0185: Newly corrected services:
service jboss.naming.context.java.queue.demo (new available)
{code}
App now works.
> Redeploy deployment if all missing dependencies for deployment are corrected
> -----------------------------------------------------------------------------
>
> Key: WFCORE-1912
> URL: https://issues.jboss.org/browse/WFCORE-1912
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Server
> Reporter: Miroslav Novak
> Assignee: Jason Greene
> Labels: user_experience
>
> If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable.
> For example if you deploy EJB which injects queue like:
> {code}
> @Resource(mappedName = "java:/jms/queue/OutQueue")
> private Queue outQueue;
> {code}
> and administrator deploys queue later then EJB would automatically get redeployed.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-7194:
------------------------------------
[~dmlloyd], what about key manager? is it analogy to trust manager? So {{KeyManagerFactory.getDefaultAlgorithm()}} can be used in elytron code whenever user don't explicitly define algorithm?
> Simplify creation of trust/key-manager in elytron
> -------------------------------------------------
>
> Key: WFLY-7194
> URL: https://issues.jboss.org/browse/WFLY-7194
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> If I want to setup TLS [1], I have to create key manager with CLI command
> {code}
> /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509")
> {code}
> 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used.
> 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone.
> 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required.
> {code}
> <xs:attribute name="key-store" type="xs:string" use="optional">
> <xs:annotation>
> <xs:documentation>
> Reference to the KeyStore to use with the KeyManager.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> {code}
> 4.{{password}} attribute is optional, probably should be required
> {code}
> "password" => {
> "type" => STRING,
> "description" => "The password to use when initialising the underlying KeyManagerFactory.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "1.0.0",
> "reason" => "Will be updated to use proper CredentialStore references."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {code}
> [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7194) Simplify creation of trust/key-manager in elytron
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-7194?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-7194:
-----------------------------------
The trust manager definitely should use the default algorithm when none is given; in this case the algorithm name isn't an "algorithm" per se, it's just an implementation name.
The key store definitely must require an explicit algorithm name though. Key store formats are determined by algorithm name, so there is no logical default for this value.
> Simplify creation of trust/key-manager in elytron
> -------------------------------------------------
>
> Key: WFLY-7194
> URL: https://issues.jboss.org/browse/WFLY-7194
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> If I want to setup TLS [1], I have to create key manager with CLI command
> {code}
> /subsystem=elytron/key-managers=httpsKM:add(key-store=httpsKS,algorithm="SunX509")
> {code}
> 1. It seems to me {{algorithm}} can be optional. If not set {{TrustManagerFactory.getDefaultAlgorithm()}} can be used.
> 2. Also, please, enhance xsd/model documentation with clear statement that this {{password}} attribute is in fact "key password" . Or probably better rename attribute from {{password}} to {{key-password}} to make it absolutely clear to everyone.
> 3. {{key-store}} attribute is declared optional in xsd . In model it is properly declared as required. Please change XSD to express it is required.
> {code}
> <xs:attribute name="key-store" type="xs:string" use="optional">
> <xs:annotation>
> <xs:documentation>
> Reference to the KeyStore to use with the KeyManager.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> {code}
> 4.{{password}} attribute is optional, probably should be required
> {code}
> "password" => {
> "type" => STRING,
> "description" => "The password to use when initialising the underlying KeyManagerFactory.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "deprecated" => {
> "since" => "1.0.0",
> "reason" => "Will be updated to use proper CredentialStore references."
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {code}
> [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7219) Wrong description of missing target-name in simple-permission-mapper
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7219?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev commented on WFLY-7219:
-------------------------------------
[~honza889]: QA reopened JBEAP-6139 (see comment). Let me know if you want me to investigate it.
> Wrong description of missing target-name in simple-permission-mapper
> --------------------------------------------------------------------
>
> Key: WFLY-7219
> URL: https://issues.jboss.org/browse/WFLY-7219
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
> Fix For: 11.0.0.Alpha1
>
>
> In case when simple-permission-mapper cannot be added through CLI command due to missing target-name attribute, then IllegalArgumentException with wrong description is thrown. It says: "Parameter '*name*' may not be null". It should be "Parameter '*target-name*' may not be null".
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7207) Integration of EJB with transactions during the graceful shutdown
by Flavia Rainone (JIRA)
[ https://issues.jboss.org/browse/WFLY-7207?page=com.atlassian.jira.plugin.... ]
Flavia Rainone commented on WFLY-7207:
--------------------------------------
Thanks for the PR, [~gytis], I can write the rest of the code for this Jira if [~dmlloyd] hasn't already started.
> Integration of EJB with transactions during the graceful shutdown
> -----------------------------------------------------------------
>
> Key: WFLY-7207
> URL: https://issues.jboss.org/browse/WFLY-7207
> Project: WildFly
> Issue Type: Feature Request
> Components: EJB
> Reporter: Gytis Trikleris
> Assignee: David Lloyd
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> During the graceful shutdown EJB subsystem should consult Transactions subsystem whether the requests should be rejected or not. Transaction subsystem would check for availability of JTA or JTS transaction and return the outcome.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months