[JBoss JIRA] (ELY-677) Credential-reference should be resolved in time of request.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-677:
--------------------------------
Summary: Credential-reference should be resolved in time of request.
Key: ELY-677
URL: https://issues.jboss.org/browse/ELY-677
Project: WildFly Elytron
Issue Type: Bug
Components: Credential Store
Affects Versions: 1.1.0.Beta10
Reporter: Hynek Švábek
Assignee: Peter Skopek
Attachments: firefly.keystore
Credential-reference should be resolved in time of request.
When you added KeyStore to Elytron subsystem which have credential-reference to non-exists credential store then you can see this error message
{code}
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("key-store" => "firefly")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.credential-store-client.NonexistingCredentialStore"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.key-store.firefly is missing [org.wildfly.security.credential-store-client.NonexistingCredentialStore]"]
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-5227) Move security-manager subsystem from WildFly to WildFly Core
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5227?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-5227:
--------------------------------------
Assignee: Ken Wills (was: Stefan Guilhen)
As discussed in the Brno F2F, I agreed to assign someone to take responsibility for getting this done for WF 11 so [~sguilhen] can focus on elytron related work. So that will be Ken Wills. Stefan, Ken is looking into how you did your previous PRs on this; thanks for the explanations which seem simple enough. He'll coordinate with you and [~dlofthouse] to work out when making this move would be least disruptive to the elytron work.
> Move security-manager subsystem from WildFly to WildFly Core
> ------------------------------------------------------------
>
> Key: WFLY-5227
> URL: https://issues.jboss.org/browse/WFLY-5227
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager
> Reporter: Josef Cacek
> Assignee: Ken Wills
> Priority: Critical
>
> It's not possible to define security permissions in WildFly Core without {{security-manager}} subsystem. Therefore the subsystem should be moved from WildFly to the Core.
> More details in the [Permissions in WildFly Core|http://lists.jboss.org/pipermail/wildfly-dev/2015-August/thread.html...] thread on {{wildfly-dev}} mailing list.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFCORE-1865) Make the authentication configurable in the testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1865?page=com.atlassian.jira.plugi... ]
Filippe Spolti updated WFCORE-1865:
-----------------------------------
Description:
Actually some tests cases fails when running against a remote eap instance.
In this specific case instances running on Openshift v3.
In order to get those tests working we have to modify some classes to configure the authentication.
> Make the authentication configurable in the testsuite
> -----------------------------------------------------
>
> Key: WFCORE-1865
> URL: https://issues.jboss.org/browse/WFCORE-1865
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
>
> Actually some tests cases fails when running against a remote eap instance.
> In this specific case instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
Filippe Spolti updated WFLY-7309:
---------------------------------
Summary: Make the authentication configurable in the testsuite (was: Make the authentication configurable in the eap testsuite )
> Make the authentication configurable in the testsuite
> ------------------------------------------------------
>
> Key: WFLY-7309
> URL: https://issues.jboss.org/browse/WFLY-7309
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
>
> Actually some tests cases fails when running against a remote eap instance.
> In this specific case instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
> Example:
> org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
> return connector.getMBeanServerConnection();
> }
> {code}
> To:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
> String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
> propEnv.put(JMXConnector.CREDENTIALS, credentials);
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
> return connector.getMBeanServerConnection();
> }
> {code}
> Could these kind of authentication being configurable?
> It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months