February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8190) Make OpenSAML private

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8190?page=com.atlassian.jira.plugin.... ] Tomaz Cerar moved JBEAP-9021 to WFLY-8190: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8190 (was: JBEAP-9021) Issue Type: Task (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.0.0.GA) > Make OpenSAML private > --------------------- > > Key: WFLY-8190 > URL: https://issues.jboss.org/browse/WFLY-8190 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > See if it can be private. We are not providing OpenSAML, we are providing SAML capability via our JEE Webservices, so storage & messaging jars must not be required to provide our JAXWS capabilities, thus we do not ship them. Right now is public so users would expect to have the storage & messaging at least in the BOM files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-972) Elytron Audit Logging does not log failed authentication

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/ELY-972?page=com.atlassian.jira.plugin.sy... ] Jan Tymel updated ELY-972: -------------------------- Attachment: deployment.war > Elytron Audit Logging does not log failed authentication > -------------------------------------------------------- > > Key: ELY-972 > URL: https://issues.jboss.org/browse/ELY-972 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Tymel > Assignee: Jan Kalina > Priority: Blocker > Attachments: deployment.war > > > Successful authentication is correctly handled by Elytron Audit Logging. However, if user provides incorrect password (~ authentication fails) there is no such record in audit log file. > Logging of failed authentication is one of the requirements for this Elytron Audit Logging feature. Therefore setting blocker priority. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/ELY-976?page=com.atlassian.jira.plugin.sy... ] Jan Tymel updated ELY-976: -------------------------- Attachment: standalone.xml > Elytron Audit Logging's event timestamp lacks information about seconds > ----------------------------------------------------------------------- > > Key: ELY-976 > URL: https://issues.jboss.org/browse/ELY-976 > Project: WildFly Elytron > 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)

9 years, 2 months

1
0
0 / 0

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

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/ELY-976?page=com.atlassian.jira.plugin.sy... ] Jan Tymel updated ELY-976: -------------------------- Attachment: deployment.war > Elytron Audit Logging's event timestamp lacks information about seconds > ----------------------------------------------------------------------- > > Key: ELY-976 > URL: https://issues.jboss.org/browse/ELY-976 > Project: WildFly Elytron > 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)

9 years, 2 months

1
0
0 / 0

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

by Jan Tymel (JIRA)

Jan Tymel created ELY-976: ----------------------------- Summary: Elytron Audit Logging's event timestamp lacks information about seconds Key: ELY-976 URL: https://issues.jboss.org/browse/ELY-976 Project: WildFly Elytron Issue Type: Bug Reporter: Jan Tymel Assignee: Darran Lofthouse Priority: Blocker 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)

9 years, 2 months

1
0
0 / 0

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

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/ELY-976?page=com.atlassian.jira.plugin.sy... ] Jan Tymel reassigned ELY-976: ----------------------------- Assignee: (was: Darran Lofthouse) > Elytron Audit Logging's event timestamp lacks information about seconds > ----------------------------------------------------------------------- > > Key: ELY-976 > URL: https://issues.jboss.org/browse/ELY-976 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Tymel > Priority: Blocker > > 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)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8189) CS tool, add prompt when --secret is missing

by Martin Choma (JIRA)

Martin Choma created WFLY-8189: ---------------------------------- Summary: CS tool, add prompt when --secret is missing Key: WFLY-8189 URL: https://issues.jboss.org/browse/WFLY-8189 Project: WildFly Issue Type: Bug Components: Security Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Blocker Use case: - User have automation script using cs tool and user don't want secret value be 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 attribute. When omitting --secret attribute user interaction prompt should follow with possibility to input secret value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8188) CS tool, add prompt when --password is missing

by Martin Choma (JIRA)

Martin Choma created WFLY-8188: ---------------------------------- Summary: CS tool, add prompt when --password is missing Key: WFLY-8188 URL: https://issues.jboss.org/browse/WFLY-8188 Project: WildFly Issue Type: Bug Components: Security Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Blocker Use case: - User have automation script using cs tool and user don't want to have password stored in file. - User don't want credential store password to be stored in shell history after execution. - User don't want credential store password to be listed in {{ps -aux}} output. There have to be possibility to omit --password attribute. When omitting --password attribute user interaction prompt should follow with possibility to input password. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8187) CS tool, omitting required param leads to NPE

by Martin Choma (JIRA)

Martin Choma created WFLY-8187: ---------------------------------- Summary: CS tool, omitting required param leads to NPE Key: WFLY-8187 URL: https://issues.jboss.org/browse/WFLY-8187 Project: WildFly Issue Type: Bug Components: Security Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Blocker Omitting required param leads to NPE, e.g. when adding alias without password (-p --password) {code} java -jar wildfly-elytron-tool.jar credential-store -a test_alis -x admin123 -c -u "cr-store://store-test-1?create=true" -salt 12345678 --iteration 230 Exception in thread "main" java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Matcher.java:1283) at java.util.regex.Matcher.reset(Matcher.java:309) at java.util.regex.Matcher.<init>(Matcher.java:229) at java.util.regex.Pattern.matcher(Pattern.java:1093) at java.util.Formatter.parse(Formatter.java:2547) at java.util.Formatter.format(Formatter.java:2501) at java.io.PrintStream.format(PrintStream.java:970) at java.io.PrintStream.printf(PrintStream.java:871) at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:58) {code} Help does not document required options. If required option is ommited user is not informed about which parameter is missing. So effectivelly user have no way to find out required parameters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8186) CS tool, can't list --help without NPE occurence

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8186?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-8186: ------------------------------- Labels: credential-store (was: ) > CS tool, can't list --help without NPE occurence > ------------------------------------------------ > > Key: WFLY-8186 > URL: https://issues.jboss.org/browse/WFLY-8186 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > Labels: credential-store > > {code} > java -jar wildfly-elytron-tool.jar credential-store -h > {code} > or because of WFLY-8176 > {code} > java -jar wildfly-elytron-tool.jar credential-store -h --salt 12345678 --iteration 230 > {code} > leads to > {code} > usage: java -jar wildfly-elytron-tool.jar credential-store <sub-command> > <options> -a <arg> | -e <arg> | -h | -r <arg> | -v [-c] [-f] [-i > <arg>] [-l <arg>] [-p <arg>] [-s <arg>] [-t <arg>] [-u <arg>] [-x > <arg>] > Exception in thread "main" java.lang.NullPointerException > at java.util.regex.Matcher.getTextLength(Matcher.java:1283) > at java.util.regex.Matcher.reset(Matcher.java:309) > at java.util.regex.Matcher.<init>(Matcher.java:229) > at java.util.regex.Pattern.matcher(Pattern.java:1093) > at java.util.Formatter.parse(Formatter.java:2547) > at java.util.Formatter.format(Formatter.java:2501) > at java.io.PrintStream.format(PrintStream.java:970) > at java.io.PrintStream.printf(PrintStream.java:871) > at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:58) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

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 February 2017