June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8904) Fix AuthenticationTestCase for Elytron and unignore it

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFLY-8904?page=com.atlassian.jira.plugin.... ] Michal Jurc moved JBEAP-11395 to WFLY-8904: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8904 (was: JBEAP-11395) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.DR19) > Fix AuthenticationTestCase for Elytron and unignore it > ------------------------------------------------------ > > Key: WFLY-8904 > URL: https://issues.jboss.org/browse/WFLY-8904 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Michal Jurc > Assignee: Michal Jurc > > {{org.jboss.as.test.integration.ejb.security.AuthenticationTestCase}} currently fails in {{elytron}} profile due to different exception than expected being produced by Elytron: > {code}Results : > Failed tests: > AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:257 null > {code} > When this is fixed, the test should be unignored for the {{elytron}} profile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1607) Internal refactor removing KnowledgeBase in preparation for DROOLS-1583

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1607: -------------------------------------- Summary: Internal refactor removing KnowledgeBase in preparation for DROOLS-1583 Key: DROOLS-1607 URL: https://issues.jboss.org/browse/DROOLS-1607 Project: Drools Issue Type: Sub-task Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2193) View: use View.getCoord() to determine coordinator

by Bela Ban (JIRA)

Bela Ban created JGRP-2193: ------------------------------ Summary: View: use View.getCoord() to determine coordinator Key: JGRP-2193 URL: https://issues.jboss.org/browse/JGRP-2193 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 4.0.4 Often the coord is determined by getting a view's members and grabbing the first member of the view. If the list is empty, this fails with an NPE. Instead, use {{View.getCoord()}} and handle the potential null value. {noformat} ViewId vid = new ViewId(new JGAddress(), 0); List<Address> members = new ArrayList<>(); View jgv = new View(vid, members); this.myChannel.down(new Event(Event.VIEW_CHANGE, jgv)); java.lang.ArrayIndexOutOfBoundsException: 0 at java.util.Arrays$ArrayList.get(Arrays.java:3841) at java.util.Collections$UnmodifiableList.get(Collections.java:1309) at org.jgroups.protocols.pbcast.STABLE.handleViewChange(STABLE.java:365) at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:328) at org.jgroups.protocols.FlowControl.down(FlowControl.java:347) at org.jgroups.protocols.FlowControl.down(FlowControl.java:347) at org.jgroups.protocols.FRAG2.down(FRAG2.java:136) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1039) at org.jgroups.JChannel.down(JChannel.java:790) at org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:310) {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1231) WildFly Elytron Tool, Vault commands with --enc-dir option leads to directory which doesn't contain VAULT.dat should fail.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-1231: --------------------------------- Summary: WildFly Elytron Tool, Vault commands with --enc-dir option leads to directory which doesn't contain VAULT.dat should fail. Key: ELY-1231 URL: https://issues.jboss.org/browse/ELY-1231 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse Priority: Blocker Vault commands with --enc-dir option leads to directory which doesn't contain VAULT.dat should fail. Converted credential store storage file is empty but it is very confusing to see successful message and created credential storage file. The user might mistakenly believe that the VAULT.dat was empty. *How to reproduce* set --enc-dir to folder which is empty. {code} ./elytron-tool.sh vault --enc-dir /tmp/empty_dir --keystore server.store --keystore-password secretsecret --location converted001.store --alias jboss Vault (enc-dir="/tmp";keystore="server.store") converted to credential store "converted001.store" {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1231) WildFly Elytron Tool, Vault commands with --enc-dir option leads to directory which doesn't contain VAULT.dat should fail.

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-1231?page=com.atlassian.jira.plugin.s... ] Hynek Švábek reassigned ELY-1231: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > WildFly Elytron Tool, Vault commands with --enc-dir option leads to directory which doesn't contain VAULT.dat should fail. > -------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1231 > URL: https://issues.jboss.org/browse/ELY-1231 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > Priority: Blocker > > Vault commands with --enc-dir option leads to directory which doesn't contain VAULT.dat should fail. > Converted credential store storage file is empty but it is very confusing to see successful message and created credential storage file. > The user might mistakenly believe that the VAULT.dat was empty. > *How to reproduce* > set --enc-dir to folder which is empty. > {code} > ./elytron-tool.sh vault --enc-dir /tmp/empty_dir --keystore server.store --keystore-password secretsecret --location converted001.store --alias jboss > Vault (enc-dir="/tmp";keystore="server.store") converted to credential store "converted001.store" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-887) "Deprecate" using an expression in model refs to interfaces

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-887?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-887: --------------------------------- Fix Version/s: 3.0.0.Beta26 (was: 3.0.0.Beta25) > "Deprecate" using an expression in model refs to interfaces > ----------------------------------------------------------- > > Key: WFCORE-887 > URL: https://issues.jboss.org/browse/WFCORE-887 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Beta26 > > > SocketBindingGroupResourceDefinition and OutboundSocketBindingResourceDefinition both have attributes that represent model refs to interface resources, but which also allow expressions. > Model references should not allow expressions. These were "grandfathered in" when the large scale expression support roll out happened for AS 7.2 / EAP 6.1. > There's no metadata facility to record that expression support is deprecated, but the add handler for these should log a WARN if they encounter an expression. Hopefully in EAP 8 we can then remove expression support. > We should look for other cases like this too, although those changes should be separate JIRAs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1606) Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1606?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1606: ---------------------------------- Fix Version/s: 3.0.0.Beta26 (was: 3.0.0.Beta25) > Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1606 > URL: https://issues.jboss.org/browse/WFCORE-1606 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.0.10.Final > Reporter: Ondrej Lukas > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Beta26 > > > When security-realm, which is set as http-interface security-realm in management-interfaces, is modified and operation used {allow-resource-service-restart=true} header then server is NOT in reload-required state but modified security realm does not work correctly until server is manually reloaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2100) Upgrade to WildFly Elytron 1.1.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2100?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-2100: ---------------------------------- Fix Version/s: 3.0.0.Beta26 (was: 3.0.0.Beta25) > Upgrade to WildFly Elytron 1.1.0.Final > -------------------------------------- > > Key: WFCORE-2100 > URL: https://issues.jboss.org/browse/WFCORE-2100 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta26 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1897) Follow up WFCORE-296 once migrated to Remoting 5

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1897?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1897: ---------------------------------- Fix Version/s: 3.0.0.Beta26 (was: 3.0.0.Beta25) > Follow up WFCORE-296 once migrated to Remoting 5 > ------------------------------------------------ > > Key: WFCORE-1897 > URL: https://issues.jboss.org/browse/WFCORE-1897 > Project: WildFly Core > Issue Type: Task > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta26 > > > WFCORE-296 adds support for the schemes remote:// remote_http:// and remote+https:// - once we switch to centralised Endpoints we need to ensure this new set is still supported along with the previous set. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2016) Change sasl-authentication-factor for management auth works after reload, but not after server restart

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2016?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-2016: ---------------------------------- Fix Version/s: 3.0.0.Beta26 (was: 3.0.0.Beta25) > Change sasl-authentication-factor for management auth works after reload, but not after server restart > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-2016 > URL: https://issues.jboss.org/browse/WFCORE-2016 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Zach Rhoads > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta26 > > > I can successfully configure a new sasl-authentication-factory and assign it to the management interface: > {code} > /subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add() > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:set-password(clear={password="password123"}) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=user1:add-attribute(name=Roles, value=["Admin","Guest"]) > /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) > /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper) > /subsystem=elytron/sasl-authentication-factory=example-sasl-auth:add(sasl-server-factory=configured,security-domain=exampleFsSD,mechanism-configurations=[{mechanism-name=DIGEST-MD5,mechanism-realm-configurations=[{realm-name=exampleSaslRealm}]}]) > /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=example-sasl-auth) > reload > {code} > after reload, i am forced to re-authenticate and it succeeds: > {code} > [standalone@localhost:9990 /] reload > Authenticating against security realm: exampleSaslRealm > Username: user1 > Password: > [standalone@localhost:9990 /] > {code} > Once i restart the server though and try to connect, i get a timeout: > {code} > $ ./jboss-cli.sh -c > Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out > {code} > It also fails if i force no local auth: > {code} > $ ./jboss-cli.sh -c --no-local-auth > Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out: WFLYPRT0023: Could not connect to remote+http://localhost:9990. The connection timed out > {code}/ -- 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 June 2017