[
https://issues.redhat.com/browse/WFCORE-5103?page=com.atlassian.jira.plug...
]
Farah Juma commented on WFCORE-5103:
------------------------------------
[~jdenise] This looks like it might just be a configuration issue. If you specify the
{{type}} attribute, the operation will succeed:
{{/subsystem=elytron/key-store=keystore:add(path="/etc/foo/keystore.jks",
credential-reference={clear-text=${keystore.password}}, type=JKS)}}
[~mmazanek] From your work on WFCORE-4058, do you remember if this behaviour is
intentional? i.e., Is it expected that if the file that backs a {{key-store}} doesn't
exist then the {{type}} attribute must be specified even if the file is not required to
exist at the time the {{KeyStore}} service starts?
Adding non existent and not required keystore fails
---------------------------------------------------
Key: WFCORE-5103
URL:
https://issues.redhat.com/browse/WFCORE-5103
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Jean Francois Denise
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 13.0.0.Beta6
We are in a case where a CLI script is executed in an embedded server. They keystore
added doesn't exist locally when the script is run. The operation is:
/subsystem=elytron/key-store=keystore:add(required=false,
path="/etc/foo/keystore.jks",
credential-reference=\{clear-text=${keystore.password}})
Error:
"failure-description" => {"WFLYCTL0080: Failed services" =>
{"org.wildfly.security.key-store.keystore" => "WFLYELY00004: Unable to
start the service.
[ERROR] Caused by: org.jboss.msc.service.StartException in anonymous service:
WFLYELY00022: KeyStore file '/etc/wf-secrets/keystore.jks' does not exist and
required."}},
--
This message was sent by Atlassian Jira
(v7.13.8#713008)