[JBoss JIRA] (WFLY-7970) Elytron keystore type default value
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7970?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev reassigned WFLY-7970:
-----------------------------------
Assignee: Ilia Vassilev
> Elytron keystore type default value
> -----------------------------------
>
> Key: WFLY-7970
> URL: https://issues.jboss.org/browse/WFLY-7970
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
>
> Make attribute type optional during key-store creation. If not set default value "JKS" can be used.
> Basically in this issue is requesting same behaviour as legacy keystore in realms
> {code:jsonl|title=ManagementModel}
> "keystore-provider" => {
> "type" => STRING,
> "description" => "The provider for loading the keystore, defaults to JKS.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "JKS",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {code}
> Extracted from WFLY-7125 and tracked as separate issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8157) Synchronize XSD and DMR description of credential-store attributes
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-8157?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev reassigned WFLY-8157:
-----------------------------------
Assignee: Ilia Vassilev (was: Darran Lofthouse)
> Synchronize XSD and DMR description of credential-store attributes
> ------------------------------------------------------------------
>
> Key: WFLY-8157
> URL: https://issues.jboss.org/browse/WFLY-8157
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
> Labels: credential-store
>
> Use XSD description in DMR description, because description in XSD is better for attributes
> * provider-name
> * providers
> * other-providers
> * relative-to
> * uri (DMR description contains wrong vault://)
> For {{type}} attribute use this description in both XSD and DMR: "The credential store type, e.g. KeyStoreCredentialStore" . Now there is mentioned wrongly KeyStorePasswordStore
> {code:xml|title=XSD}
> <xs:attribute name="type" type="xs:string" use="optional">
> <xs:annotation>
> <xs:documentation>
> The credential store type, e.g. KeyStorePasswordStore.
> </xs:documentation>
> </xs:annotation>
> </xs:attribute>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8241) EJB deployments with Elytron SD collides in EJB3 SD service
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-8241?page=com.atlassian.jira.plugin.... ]
Farah Juma commented on WFLY-8241:
----------------------------------
This was fixed in WFLY-8171:
https://github.com/wildfly/wildfly/pull/9681
> EJB deployments with Elytron SD collides in EJB3 SD service
> -----------------------------------------------------------
>
> Key: WFLY-8241
> URL: https://issues.jboss.org/browse/WFLY-8241
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Attachments: enable-elytron.cli, read-props-grant.ear, read-props-limited.ear
>
>
> Every EJB deployment associated with an Elytron security domain builds *jboss.ejb3.security-domain* service:
> https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo...
> But it fails if there are more such deployments, because it mean second service with the same name:
> {code}
> 00:02:12,118 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.subunit."read-props-limited.ear"."ejb-moduleread-props-limited.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."read-props-limited.ear"."ejb-moduleread-props-limited.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "ejb-moduleread-props-limited.jar" of deployment "read-props-limited.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> 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: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb3.security-domain is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.ejb3.deployment.processors.EJBDefaultSecurityDomainProcessor.deploy(EJBDefaultSecurityDomainProcessor.java:111)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months