May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1162) WildFly Elytron Tool, add prompt when --secret is missing for Mask command.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-1162: --------------------------------- Summary: WildFly Elytron Tool, add prompt when --secret is missing for Mask command. Key: ELY-1162 URL: https://issues.jboss.org/browse/ELY-1162 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse Priority: Critical Add prompt when --secret is missing for Mask command. Use case: User have automation script using wildfly elytron tool and user don't want to have secret value stored in file. User don't want secret value to be stored in shell history after execution. User don't want secret value to be listed in ps -aux output. There have to be possibility to omit --secret. When omitting --secret attribute user interaction prompt should follow with possibility to input secret value. *How to reproduce* {code} java -jar .wildfly-elytron-tool.jar mask -i 240 -s 12345678 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2691) Elytron modifiable realms should show existing identities in subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2691?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-2691: ------------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly-core/pull/150 (was: https://github.com/wildfly-security-incubator/wildfly-core/pull/150, https://github.com/wildfly/wildfly-core/pull/2420) > Elytron modifiable realms should show existing identities in subsystem > ---------------------------------------------------------------------- > > Key: WFCORE-2691 > URL: https://issues.jboss.org/browse/WFCORE-2691 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta15 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Labels: filesystem-realm, security-realm > Fix For: 3.0.0.Beta22 > > > Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in: > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"elytron\"), > (\"filesystem-realm\" => \"realm\"), > (\"identity\" => \"user\") > ]' not found", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add > { > "outcome" => "failed", > "failure-description" => "WFLYELY01000: Identity with name [user] already exists.", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8778) Elytron filesystem-realm should load existing identities from file system

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8778?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-8778: ----------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly/pull/204 (was: https://github.com/wildfly/wildfly/pull/10064) > Elytron filesystem-realm should load existing identities from file system > ------------------------------------------------------------------------- > > Key: WFLY-8778 > URL: https://issues.jboss.org/browse/WFLY-8778 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Labels: filesystem-realm, security-realm > > Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in: > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"elytron\"), > (\"filesystem-realm\" => \"realm\"), > (\"identity\" => \"user\") > ]' not found", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add > { > "outcome" => "failed", > "failure-description" => "WFLYELY01000: Identity with name [user] already exists.", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1062) caching-realm with ldap-realm cannot be added when LDAP is unreachable

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/ELY-1062?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski updated ELY-1062: ------------------------------------ Fix Version/s: 1.1.0.Beta43 > caching-realm with ldap-realm cannot be added when LDAP is unreachable > ---------------------------------------------------------------------- > > Key: ELY-1062 > URL: https://issues.jboss.org/browse/ELY-1062 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.1.0.Beta43 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1565) Implement a KieScanner listener

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1565?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi commented on DROOLS-1565: ------------------------------------------- [~tari_manga], yeah, getting them in one shot would be fine. Thanks! > Implement a KieScanner listener > ------------------------------- > > Key: DROOLS-1565 > URL: https://issues.jboss.org/browse/DROOLS-1565 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Matteo Mortari > > Allow to register a listener on the KieScanner to be notified when a kjar is successfully updated and when the incremental compilation fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1091) CS tool, Summary output must reflect chosen option, now there is always CLI command for add new credential store.

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ELY-1091?page=com.atlassian.jira.plugin.s... ] Yeray Borges updated ELY-1091: ------------------------------ Git Pull Request: https://github.com/wildfly-security/wildfly-elytron-tool/pull/39, https://github.com/wildfly-security/wildfly-elytron-tool/pull/64 (was: https://github.com/wildfly-security/wildfly-elytron-tool/pull/39) > CS tool, Summary output must reflect chosen option, now there is always CLI command for add new credential store. > ----------------------------------------------------------------------------------------------------------------- > > Key: ELY-1091 > URL: https://issues.jboss.org/browse/ELY-1091 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Yeray Borges > Priority: Critical > > Summary output must reflect chosen option. When I run wildfly-elytron-tool with --remove and --summary I always get "add command for CLI" > There is expected command for remove entry from credential store. > Same problem is there for --aliases, --exists > {code} > java -jar wildfly-elytron-tool.jar credential-store --remove secret_alias --password pass123 --uri "cr-store://test1.jceks?modifiable=true;create=true;keyStoreType=JCEKS" -l test1.jceks --summary > Alias "secret_alias" has been successfully removed > Credential store command summary: > -------------------------------------- > /subsystem=elytron/credential-store=test:add(uri="cr-store://test1.jceks?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="pass123"}) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8793) Change attributes of services in EJB3 subsystem to be allow runtime modifications

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-8793?page=com.atlassian.jira.plugin.... ] Michal Jurc updated WFLY-8793: ------------------------------ Priority: Major (was: Critical) > Change attributes of services in EJB3 subsystem to be allow runtime modifications > --------------------------------------------------------------------------------- > > Key: WFLY-8793 > URL: https://issues.jboss.org/browse/WFLY-8793 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Michal Jurc > Assignee: David Lloyd > > Currently, almost all of the attributes of services in {{/subsystem=ejb3}} have {{"restart-required" => "all-services"}}. This should be changed to allow these attributes to be modifiable in runtime where possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8793) Change attributes of services in EJB3 subsystem to be allow runtime modifications

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-8793?page=com.atlassian.jira.plugin.... ] Michal Jurc moved JBEAP-10956 to WFLY-8793: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8793 (was: JBEAP-10956) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Affects Version/s: (was: 7.1.0.DR18) > Change attributes of services in EJB3 subsystem to be allow runtime modifications > --------------------------------------------------------------------------------- > > Key: WFLY-8793 > URL: https://issues.jboss.org/browse/WFLY-8793 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Michal Jurc > Assignee: David Lloyd > Priority: Critical > > Currently, almost all of the attributes of services in {{/subsystem=ejb3}} have {{"restart-required" => "all-services"}}. This should be changed to allow these attributes to be modifiable in runtime where possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-157) Provide faster alternative to SimpleDataFormat

by Koen Janssens (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-157?page=com.atlassian.jira.plugin... ] Koen Janssens updated LOGMGR-157: --------------------------------- Attachment: DateFormatPerformance.java > Provide faster alternative to SimpleDataFormat > ---------------------------------------------- > > Key: LOGMGR-157 > URL: https://issues.jboss.org/browse/LOGMGR-157 > Project: JBoss Log Manager > Issue Type: Enhancement > Components: core > Affects Versions: 2.0.6.Final > Reporter: Koen Janssens > Attachments: DateFormatPerformance.java > > > Whenever a data or timestamp is included in the logging pattern, SimpleDataFormat is used for formatting. Even with one instance per thread, it is still a heavy beast. > Other logging libraries (like the 15 year old log4j) have 'fast tracks' for known formats such as ISO 8601. These implementations are faster and generate less memory garbage. > During profiling, i discovered that simpledateformat is doing a lot of stuff while printing a date: > at java.lang.Thread.run(Thread.java:748) > at org.jboss.logmanager.handlers.AsyncHandler$AsyncTask.run(AsyncHandler.java:196) > at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76) > at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:46) > at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:32) > at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:83) > at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:224) > at org.jboss.logmanager.formatters.Formatters$5.renderRaw(Formatters.java:389) > at java.text.DateFormat.format(DateFormat.java:345) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:936) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:966) > at java.text.SimpleDateFormat.subFormat(SimpleDateFormat.java:1125) > at java.util.Calendar.getDisplayName(Calendar.java:2110) > at java.text.DateFormatSymbols.getInstance(DateFormatSymbols.java:340) > at java.text.DateFormatSymbols.getProviderInstance(DateFormatSymbols.java:364) > at sun.util.locale.provider.DateFormatSymbolsProviderImpl.getInstance(DateFormatSymbolsProviderImpl.java:85) > at java.text.DateFormatSymbols.<init>(DateFormatSymbols.java:145) > at java.text.DateFormatSymbols.initializeData(DateFormatSymbols.java:710) > at sun.util.resources.LocaleData.getDateFormatData(LocaleData.java:127) > at sun.util.resources.LocaleData.getBundle(LocaleData.java:163) > at java.security.AccessController.doPrivileged(Native Method) > at sun.util.resources.LocaleData$1.run(LocaleData.java:163) > at sun.util.resources.LocaleData$1.run(LocaleData.java:167) > at java.util.ResourceBundle.getBundle(ResourceBundle.java:890) > at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1348) > at java.util.ResourceBundle.checkList(ResourceBundle.java:1400) > at java.util.Collections$UnmodifiableCollection.isEmpty(Collections.java:1031) > at java.util.AbstractCollection.isEmpty(AbstractCollection.java:86) > I have attached a small comparision between simpledateformat performance and log4j ISO formatting performance. It roughly a factor 10 'faster' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1565) Implement a KieScanner listener

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1565?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1565: ---------------------------------------- [~tkobayashi] for my understanding, I am proceeding with the assumption it is okay to return the "collect" of messages from the both phases in one shot, and notify the listener with the overall result. Also because if first phase ("build") contains any error, won't proceed to the second phase.("updateDependencyToVersion"). I just prefer to verify this, if there's a use case to receive them separately, kindly let me know. Thank you. > Implement a KieScanner listener > ------------------------------- > > Key: DROOLS-1565 > URL: https://issues.jboss.org/browse/DROOLS-1565 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Matteo Mortari > > Allow to register a listener on the KieScanner to be notified when a kjar is successfully updated and when the incremental compilation fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2017