April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-83) Create test cases for hawkular-wildfly-agent-installer.jar

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-83?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-83: ------------------------------------------ Created polarion test run template [1] on which all test cases will be added. Execution will be done as another run in polarion based on this template. https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > Create test cases for hawkular-wildfly-agent-installer.jar > ---------------------------------------------------------- > > Key: HAWKULARQE-83 > URL: https://issues.jboss.org/browse/HAWKULARQE-83 > Project: Hawkular QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Hayk Hovsepyan > > hawkular-wildfly-agent-installer.jar has following options: > Options: > -D, --D Defines system properties to set > --installer-config Installer .properties configuration file > --encryption-key If specified, this is used to decode the properties that were encrypted. If you do not provide a value with the option, you will be prompted for one. > --encryption-salt The salt used for generating the key. Recommended, if encryption is used. If not specified, the same value as the key will be used. > --enabled Indicates if the agent should be enabled at startup > --config-only Skip installation of the add-ons modules, and only update the server config (e.g. standalone.xml). > --target-location Target home directory of the application server where the agent is to be installed > --module-dist Hawkular WildFly Agent Module distribution zip file - can be a file path or URL > --server-url Server URL where the agent will send its monitoring data. This is a string to be set as the storage adapter URL. > --download-server-url Server URL from which the installer will download content it may need. If not specified and the installer needs to download something then --server-url will be used. > --target-config The target configuration file to write to. Can be either absolute path or relative to target-location > --subsystem-snippet Customized subsystem XML content that overrides the default subsystem configuration > --managed-server-name The agent will use this name to refer to the server where it is deployed and locally managing. > --feed-id The feed ID that the agent will use to identify its data. > --tenant-id The tenant ID that the agent will ask to be used. Usually only used when in metrics-only mode. > --metrics-only If true, the agent will be configured to run in metrics-only mode (inventory will not be stored and no websocket connection to a Hawkular Server will be made.) If true, you must specify a tenant-id. > --managed-server-resource-type-sets If true, the agent will be configured to monitor these resource type sets. If not provided, a default set will be used based on the type of application server where the agent is being installed into (standalone or domain). > --keystore-path Keystore file. Required when server-url protocol is https > --keystore-password Keystore password. When server-url protocol is https and this option is not passed, installer will ask for password > --username User the agent will use when connecting to Hawkular Server. > --password Credentials agent will use when connecting to Hawkular Server. > We need to create test cases to cover that -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4383) Wrong order of elements in appclient.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4383?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4383: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1195138 Bugzilla Update: Perform > Wrong order of elements in appclient.xml > ------------------------------------------ > > Key: WFLY-4383 > URL: https://issues.jboss.org/browse/WFLY-4383 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 9.0.0.Alpha1 > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 9.0.0.Beta1 > > > Description of problem: > File appclient/configuration/appclient.xml has an incorrect order of elements. <core-environment> tag should be before <recovery-environment /> tag. These tags is in <subsystem xmlns="urn:jboss:domain:transactions:1.4"> and schema is in docs/schema/jboss-as-txn_1_4.xsd. This schema defines specific order of elements. > Version-Release number of selected component (if applicable): > 6.4.0.ER2 > Validate logs: > appclient/configuration/appclient.xml:150: element recovery-environment: Schemas validity error : Element '{urn:jboss:domain:transactions:1.4}recovery-environment': This element is not expected. Expected is ( {urn:jboss:domain:transactions:1.4}core-environment ). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2625) Elytron Audit Logging's event timestamp lacks information about seconds

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2625?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-2625: ------------------------------------ Assignee: Yeray Borges > Elytron Audit Logging's event timestamp lacks information about seconds > ----------------------------------------------------------------------- > > Key: WFCORE-2625 > URL: https://issues.jboss.org/browse/WFCORE-2625 > Project: WildFly Core > Issue Type: Bug > Reporter: Jan Tymel > Assignee: Yeray Borges > Priority: Blocker > Attachments: deployment.war, standalone.xml > > > The format of Elytron Audit Logging's event timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users. > Furthermore the format of timestamp is inconsistent with the one used in Management Audit Logging: > _Elytron Audit Logging:_ > {code} > 2/22/17 9:08 AM > {code} > _Management Audit Logging:_ > {code} > 2017-02-22 09:08:00 > {code} > Suggestions for improvement: > Use the same format of timestamp in Elytron Audit Logging as is already used in Management Audit Logging. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2625) Elytron Audit Logging's event timestamp lacks information about seconds

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2625?page=com.atlassian.jira.plugi... ] Yeray Borges moved ELY-976 to WFCORE-2625: ------------------------------------------ Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-2625 (was: ELY-976) > Elytron Audit Logging's event timestamp lacks information about seconds > ----------------------------------------------------------------------- > > Key: WFCORE-2625 > URL: https://issues.jboss.org/browse/WFCORE-2625 > Project: WildFly Core > Issue Type: Bug > Reporter: Jan Tymel > Priority: Blocker > Attachments: deployment.war, standalone.xml > > > The format of Elytron Audit Logging's event timestamp is insufficient. It lacks the information about seconds which might be a problem in an environment with thousands of active users. > Furthermore the format of timestamp is inconsistent with the one used in Management Audit Logging: > _Elytron Audit Logging:_ > {code} > 2/22/17 9:08 AM > {code} > _Management Audit Logging:_ > {code} > 2017-02-22 09:08:00 > {code} > Suggestions for improvement: > Use the same format of timestamp in Elytron Audit Logging as is already used in Management Audit Logging. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8510) Update EJB client to 4.0.0.Beta24

by David Lloyd (JIRA)

David Lloyd created WFLY-8510: --------------------------------- Summary: Update EJB client to 4.0.0.Beta24 Key: WFLY-8510 URL: https://issues.jboss.org/browse/WFLY-8510 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1059) When I set iteration value as STRING or NEGATIVE integer then I get different error messages.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-1059: --------------------------------- Summary: When I set iteration value as STRING or NEGATIVE integer then I get different error messages. Key: ELY-1059 URL: https://issues.jboss.org/browse/ELY-1059 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse When I set iteration value as STRING or NEGATIVE integer then I get different error messages rather the same one. {code} [hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar mask -x secret_password -s 12345678 --iteration="-123" ELY03025: Iteration count not specified for password based encryption [hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar mask -x secret_password -s 12345678 --iteration="ab123" java.lang.NumberFormatException: For input string: "ab123" {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8509) Add SHA1 to wildfly.org downloads

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8509: --------------------------------- Summary: Add SHA1 to wildfly.org downloads Key: WFLY-8509 URL: https://issues.jboss.org/browse/WFLY-8509 Project: WildFly Issue Type: Enhancement Reporter: Tomaz Cerar Assignee: Jason Greene We should have some checksum like md5 of sha1 as part of downloads on http://wildfly.org/downloads/ They are available in maven repos, maybe we could use that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8508) Unignore FormAuthUnitTestCase when running with Elytron profile

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8508?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-8508: --------------------------------- Assignee: Josef Cacek > Unignore FormAuthUnitTestCase when running with Elytron profile > --------------------------------------------------------------- > > Key: WFLY-8508 > URL: https://issues.jboss.org/browse/WFLY-8508 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > As the original issue JBEAP-9106 is fixed now, the {{FormAuthUnitTestCase}} should be unignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7949) Missing a simple way to enable Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7949?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7949: ---------------------------------- PR adding switch -Delytron for tests outside of testsuite/integration: https://github.com/wildfly-security-incubator/wildfly/pull/176 > Missing a simple way to enable Elytron > -------------------------------------- > > Key: WFLY-7949 > URL: https://issues.jboss.org/browse/WFLY-7949 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Jan Kalina > Priority: Critical > Labels: user_experience > > There should be a simple way (e.g. a CLI script provided with AS distribution) which would enable the Elytron in subsystems. As the {{standalone-elytron.xml}} profile was removed now, users don't have a one-step way to use the Elytron. > I've put some CLI commands together for my testing, but I doubt this is a complete solution: > http://javlog.cacek.cz/2017/01/enable-elytron-in-wildfly.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7949) Missing a simple way to enable Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7949?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7949: ----------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly/pull/176 > Missing a simple way to enable Elytron > -------------------------------------- > > Key: WFLY-7949 > URL: https://issues.jboss.org/browse/WFLY-7949 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Jan Kalina > Priority: Critical > Labels: user_experience > > There should be a simple way (e.g. a CLI script provided with AS distribution) which would enable the Elytron in subsystems. As the {{standalone-elytron.xml}} profile was removed now, users don't have a one-step way to use the Elytron. > I've put some CLI commands together for my testing, but I doubt this is a complete solution: > http://javlog.cacek.cz/2017/01/enable-elytron-in-wildfly.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017