November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7396: ---------------------------------- Mentioned exception handlings already added as part of ELY-680 and ELY-693. Will try to review other places... > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-7396: -------------------------------- Assignee: Jan Kalina > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1351) Calling KieRepository.getKieModule() for a GAV of a non KJar throws Exception instead of returning null as per API contract.

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1351?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1351: ---------------------------------------- API contract: {quote} * @return The KieModule identified by the given releaseId or null if such KieModule doesn't exist {quote} > Calling KieRepository.getKieModule() for a GAV of a non KJar throws Exception instead of returning null as per API contract. > ---------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1351 > URL: https://issues.jboss.org/browse/DROOLS-1351 > Project: Drools > Issue Type: Bug > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7322) LDAP referrals does not work in Elytron ldap-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7322?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-7322 at 11/2/16 5:32 AM: ----------------------------------------------------------- [~dlofthouse] Do we need *throw* mode of LDAP referrals support? If we will follow every referral, it will be equivalent of *follow* mode. Issue can be set as resolved if throw mode is not required. was (Author: honza889): [~dlofthouse] Do we need *throw* mode of LDAP referrals support? If we will follow every referral, it will be equivalent of *follow* mode. > LDAP referrals does not work in Elytron ldap-realm > -------------------------------------------------- > > Key: WFLY-7322 > URL: https://issues.jboss.org/browse/WFLY-7322 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Blocker > > LDAP referrals cannot be used in Elytron {{ldap-realm}}. Ldap Realm is currently not prepared to work with referrals at all: > * {{ldap-realm}} does not include any options which enable working with LDAP referrals (PicketBox use {{baseFilter}} option which can be configured to return also referral object) > * implementation of {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm}} does not include any logic which handles referrals > Referrals are important feature of LDAP. It has to be covered by Elytron => requested blocker flag. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1351) Calling KieRepository.getKieModule() for a GAV of a non KJar throws Exception instead of returning null as per API contract.

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1351: -------------------------------------- Summary: Calling KieRepository.getKieModule() for a GAV of a non KJar throws Exception instead of returning null as per API contract. Key: DROOLS-1351 URL: https://issues.jboss.org/browse/DROOLS-1351 Project: Drools Issue Type: Bug Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-709) SPNEGO should allow to pass custom GSSManager

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-709?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-709: -------------------------------- [~dmlloyd] Would be ok to use mechanism properties for this? (HttpServerAuthenticationMechanismFactory inteface allows to put only properties and callbackHandler into it) > SPNEGO should allow to pass custom GSSManager > --------------------------------------------- > > Key: ELY-709 > URL: https://issues.jboss.org/browse/ELY-709 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > SPNEGO mechanism (and its factory) should accept a GSSManager parameter whose default value is GSSManager.getInstance(). > See org.wildfly.security.sasl.gs2.Gs2SaslServerFactory for reference. > https://github.com/wildfly-security/wildfly-elytron/pull/534#discussion_r... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7447) Description of cluster-name attribute in replicated ha policy does not explain behavior of undefined value

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7447?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6794 to WFLY-7447: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7447 (was: JBEAP-6794) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.0.3.CR2) (was: 7.1.0.DR7) > Description of cluster-name attribute in replicated ha policy does not explain behavior of undefined value > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7447 > URL: https://issues.jboss.org/browse/WFLY-7447 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > The model enables to execute following command. > {code} > /subsystem=messaging-activemq/server=default/ha-policy=replication-master:add > {code} > It creates ha policy with following configuration. > {code} > /subsystem=messaging-activemq/server=default/ha-policy=replication-master:read-resource > { > "outcome" => "success", > "result" => { > "check-for-live-server" => false, > "cluster-name" => undefined, > "group-name" => undefined, > "initial-replication-sync-timeout" => 30000L > }, > "response-headers" => {"process-state" => "reload-required"} > {code} > From the description of {{cluster-name}} attribute it is not clear what is the behavior if this attribute is undefined. > {code} > "cluster-name" => { > "type" => STRING, > "description" => "Name of the cluster used for replication.", > "expressions-allowed" => true, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > {code} > The ActiveMQ Artemis documentation describes the attribute as follows: > bq. Name of the cluster configuration to use for replication. This setting is only necessary if you configure multiple cluster connections. If configured then the connector configuration of the cluster configuration with this name will be used when connecting to the cluster to discover if a live server is already running, see `check-for-live-server`. If unset then the default cluster connections configuration is used (the first one configured). -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7446) Typo in "consume" attribute description in security-settings

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7446?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6793 to WFLY-7446: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7446 (was: JBEAP-6793) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) > Typo in "consume" attribute description in security-settings > ------------------------------------------------------------ > > Key: WFLY-7446 > URL: https://issues.jboss.org/browse/WFLY-7446 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > Resource description of attribute {{consume}} contains following description: {noformat}his permission allows the user to consume a message from a queue bound to matching addresses.{noformat} > Could you please add missing "T" to make it "This". > This is present on > * /subsystem=messaging-activemq/server=default/security-setting - role - attribute {{consume}}, also operation add - attribute {{consume}} > * /subsystem=messaging-activemq/server=default/core-address - role - attribute {{consume}} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7445) Inconsistent description format of operation resolve-address-setting

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7445?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6792 to WFLY-7445: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7445 (was: JBEAP-6792) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) > Inconsistent description format of operation resolve-address-setting > -------------------------------------------------------------------- > > Key: WFLY-7445 > URL: https://issues.jboss.org/browse/WFLY-7445 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > Description of operation {{resolve-address-setting}} in subsystem -> messaging-activemq -> server > starts with lower case letter. All other descriptions start with upper case. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7444) "TODO" in description in messaging-activemq subsystem

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7444?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6791 to WFLY-7444: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7444 (was: JBEAP-6791) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR6) > "TODO" in description in messaging-activemq subsystem > ----------------------------------------------------- > > Key: WFLY-7444 > URL: https://issues.jboss.org/browse/WFLY-7444 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > There are 3 "TODO" in description of ActiveMQ subsystem: > {code} > "perf-blast-pages" => { > "type" => INT, > "description" => "TODO", > "attribute-group" => "debug", > "expressions-allowed" => true, > "nillable" => true, > "default" => -1, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > .... > "connector-service" => { > "description" => "TODO", > "model-description" => {"*" => { > "description" => "TODO", > "attributes" => { > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 8 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 November 2016