June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-992) org.jboss.security.Base64Encoder doesn't work for certain lengths (1026 or 3072 for example)

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/SECURITY-992?page=com.atlassian.jira.plug... ] Ilia Vassilev reassigned SECURITY-992: -------------------------------------- Assignee: Ilia Vassilev (was: Stefan Guilhen) > org.jboss.security.Base64Encoder doesn't work for certain lengths (1026 or 3072 for example) > -------------------------------------------------------------------------------------------- > > Key: SECURITY-992 > URL: https://issues.jboss.org/browse/SECURITY-992 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: PicketBox_5_1_0.Final > Reporter: Ricardo Martin Camarero > Assignee: Ilia Vassilev > Attachments: Reproducer.java > > > When a byte array of certain lengths (1026 and 3072 for example) is encoded in base64 using the class {{org.jboss.security.Base64Encoder}} the last chunk of four bytes is omitted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10553) (doc) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10553?page=com.atlassian.jira.plugin... ] Jan Kalina updated WFLY-10553: ------------------------------ Summary: (doc) CLIENT_CERT without users certificates database (was: CLIENT_CERT without users certificates database) > (doc) CLIENT_CERT without users certificates database > ----------------------------------------------------- > > Key: WFLY-10553 > URL: https://issues.jboss.org/browse/WFLY-10553 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Affects Versions: 13.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. > As client cetificate is already checked by SSLContext, certificate verification in CLIENT-CERT HTTP mechanism should be made optional. (Need to be enabled by default for backward compatibility.) > Analysis document: > https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10553) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10553?page=com.atlassian.jira.plugin... ] Jan Kalina updated WFLY-10553: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11343 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1018) > CLIENT_CERT without users certificates database > ----------------------------------------------- > > Key: WFLY-10553 > URL: https://issues.jboss.org/browse/WFLY-10553 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Affects Versions: 13.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. > As client cetificate is already checked by SSLContext, certificate verification in CLIENT-CERT HTTP mechanism should be made optional. (Need to be enabled by default for backward compatibility.) > Analysis document: > https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10553) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10553?page=com.atlassian.jira.plugin... ] Jan Kalina moved ELY-1600 to WFLY-10553: ---------------------------------------- Project: WildFly (was: WildFly Elytron) Key: WFLY-10553 (was: ELY-1600) Component/s: Documentation (was: HTTP) Affects Version/s: 13.0.0.Final (was: 1.2.0.Beta7) > CLIENT_CERT without users certificates database > ----------------------------------------------- > > Key: WFLY-10553 > URL: https://issues.jboss.org/browse/WFLY-10553 > Project: WildFly > Issue Type: Feature Request > Components: Documentation > Affects Versions: 13.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. > As client cetificate is already checked by SSLContext, certificate verification in CLIENT-CERT HTTP mechanism should be made optional. (Need to be enabled by default for backward compatibility.) > Analysis document: > https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1600) CLIENT_CERT without users certificates database

by Jan Kalina (JIRA)

Jan Kalina created ELY-1600: ------------------------------- Summary: CLIENT_CERT without users certificates database Key: ELY-1600 URL: https://issues.jboss.org/browse/ELY-1600 Project: WildFly Elytron Issue Type: Feature Request Components: HTTP Affects Versions: 1.2.0.Beta7 Reporter: Jan Kalina Assignee: Jan Kalina CLIENT_CERT http-authentication-mechanism currently requires to provide security-realm, which will contain identity for given certificate and will verify X509Evidence for it. This does not provide replacement for legacy truststore auth, which allows to use only CA certificate to authenticate users by certificates signed by CA, without any database of them. As client cetificate is already checked by SSLContext, certificate verification in CLIENT-CERT HTTP mechanism should be made optional. (Need to be enabled by default for backward compatibility.) Analysis document: https://developer.jboss.org/wiki/AnalysisDesign-CLIENTCERTWithoutUsersCer... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10532) Disable frequently failing test in clustering.web

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10532?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-10532: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Disable frequently failing test in clustering.web > ------------------------------------------------- > > Key: WFLY-10532 > URL: https://issues.jboss.org/browse/WFLY-10532 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 13.0.0.Final > Reporter: Jeff Mesnil > Assignee: Radoslav Husar > Attachments: Pull_Request_Linux_15524.log, server.log1.txt, server.log2.txt, server.log3.txt > > > Tests that fails frequently: > * ConcurrentFineWebFailoverTestCase - https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > * ReplicationForNegotiationAuthenticatorTestCase - https://ci.wildfly.org/project.html?projectId=WF_PullRequest&testNameId=-... > * CoarseWebFailoverTestCase - https://ci.wildfly.org/project.html?projectId=WF_PullRequest&testNameId=6... > This issue is distinct from WFLY-10026 as failures also occurs on Linux. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-22) [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFWIP-22?page=com.atlassian.jira.plugin.s... ] Miroslav Novak commented on WFWIP-22: ------------------------------------- Issue is still present in Artemis to 2.6.0 and Wildfly branch jmesnil/WFLY-9407_upgrade_artemis_2.4.0_with_prefix (commit 54b131dc63dfd4bb74bb44b3f8c3402964059afa) > [Artemis 2.x upgrade] MDB connected to remote server does not get activated when using discovery group with JGroups > -------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-22 > URL: https://issues.jboss.org/browse/WFWIP-22 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > Attachments: log > > > Sometimes happens that MDB does not start to consume messages from remote server. There are not warning or error messages in log. > Test Scenario: > * Start server with deployed InQueue and OutQueue > * Start 2nd server with configured pooled-connection-factory to connect to 1st server > * Deploy MDB to 2nd server - mdb is consuming messages from InQueue and sending to OutQueue > * Start sending messages to InQueue to 1st server > * Let MDB processing messages from InQueue > * Start consuming messages from OutQueue from 1st server > Pass Criteria: There is the same number of sent and received messages > Actual Result: Sometimes happens that Mdb does not start to consume messages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2629) Complex enumerations are not selected in BRL multi value constraint

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2629?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHPAM-1215 to DROOLS-2629: --------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-2629 (was: RHPAM-1215) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Enumerations Editor (was: Business Central) Affects Version/s: (was: 7.0.0.GA) QE Status: NEW Fix Version/s: (was: 7.0.1.GA) > Complex enumerations are not selected in BRL multi value constraint > ------------------------------------------------------------------- > > Key: DROOLS-2629 > URL: https://issues.jboss.org/browse/DROOLS-2629 > Project: Drools > Issue Type: Bug > Components: Enumerations Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Minor > Labels: AppFormer > > If user edits BRL multivalue contraint where previously between selected values was enumeration in the form {{"<a>, <b>, .... <c>"}}, then this enumeration is not more selected. > h2. Acceptance criteria > # Fixed steps to reproduce > ## Consequently table data can be edited (x) > ## Table can be saved and reopened (/) > # BRL condition constraint editor shown correctly > ## Date (/) > ## Readonly (/) > ## Multiselect cosntrain (/) > ## Operator requires list (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3923) Provide a profile to run enforcer rule for downstream projects - wildfly-core

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3923?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-3923: ---------------------------- Labels: downstream_dependency (was: ) > Provide a profile to run enforcer rule for downstream projects - wildfly-core > ----------------------------------------------------------------------------- > > Key: WFCORE-3923 > URL: https://issues.jboss.org/browse/WFCORE-3923 > Project: WildFly Core > Issue Type: Enhancement > Components: Build System > Reporter: Lin Gao > Assignee: Lin Gao > Labels: downstream_dependency > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3923) Provide a profile to run enforcer rule for downstream projects - wildfly-core

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3923?page=com.atlassian.jira.plugi... ] Lin Gao moved JBEAP-14866 to WFCORE-3923: ----------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3923 (was: JBEAP-14866) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) > Provide a profile to run enforcer rule for downstream projects - wildfly-core > ----------------------------------------------------------------------------- > > Key: WFCORE-3923 > URL: https://issues.jboss.org/browse/WFCORE-3923 > Project: WildFly Core > Issue Type: Enhancement > Components: Build System > Reporter: Lin Gao > Assignee: Lin Gao > Original Estimate: 4 hours > Remaining Estimate: 4 hours > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 June 2018