December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7779) ReAuth does not work with Elytron

by Jan Kalina (JIRA)

Jan Kalina created WFLY-7779: -------------------------------- Summary: ReAuth does not work with Elytron Key: WFLY-7779 URL: https://issues.jboss.org/browse/WFLY-7779 Project: WildFly Issue Type: Bug Components: Security Reporter: Jan Kalina Assignee: Darran Lofthouse -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7778) Remoting does not work with Elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7778?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7778: ----------------------------- Description: Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. Identity is unauthorized on server side. Remoting does not work because it is not implemented - this issue created primary for tests ignore issue reference. was: Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. Identity is unauthorized on server side. > Remoting does not work with Elytron > ----------------------------------- > > Key: WFLY-7778 > URL: https://issues.jboss.org/browse/WFLY-7778 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Jan Kalina > Assignee: Darran Lofthouse > Priority: Critical > > Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. > Identity is unauthorized on server side. > Remoting does not work because it is not implemented - this issue created primary for tests ignore issue reference. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7778) Remoting does not work with Elytron

by Jan Kalina (JIRA)

Jan Kalina created WFLY-7778: -------------------------------- Summary: Remoting does not work with Elytron Key: WFLY-7778 URL: https://issues.jboss.org/browse/WFLY-7778 Project: WildFly Issue Type: Bug Components: Security Reporter: Jan Kalina Assignee: Darran Lofthouse Priority: Critical Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. Identity is unauthorized on server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-828) Make PeerIdentityContext#setPeerIdentity protected

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-828?page=com.atlassian.jira.plugin.sy... ] Farah Juma closed ELY-828. -------------------------- Resolution: Rejected We can modify the ConnectionPeerIdentityContext.getCurrentIdentity() method to return the anonymous identity if the currently set peer identity is null. > Make PeerIdentityContext#setPeerIdentity protected > -------------------------------------------------- > > Key: ELY-828 > URL: https://issues.jboss.org/browse/ELY-828 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Farah Juma > Assignee: Farah Juma > > This will allow subclasses of PeerIdentityContext to be able to initialize the currently set peer identity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2104) Undertow 1.4.7.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-2104: -------------------------------------- Summary: Undertow 1.4.7.Final Key: WFCORE-2104 URL: https://issues.jboss.org/browse/WFCORE-2104 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2103) Undertow 1.4.7.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-2103: -------------------------------------- Summary: Undertow 1.4.7.Final Key: WFCORE-2103 URL: https://issues.jboss.org/browse/WFCORE-2103 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2030) sasl-authentication-factory should be valid in combination with security-realm in native management interface in CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2030?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2030: ------------------------------------- Comment: was deleted (was: The PR description didn't include this in the list of fixed issues, but I think the commit in the pr was the fix.) > sasl-authentication-factory should be valid in combination with security-realm in native management interface in CLI > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2030 > URL: https://issues.jboss.org/browse/WFCORE-2030 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Alpha15 > > > I am not able to add native management interface with both {{sasl-authentication-factory}} and {{security-realm}} attributes. According to comments in EAP7-545 Analysis document [1] setting both of them is valid configuration. However CLI consider this combination as invalid (when running server with standalone-elytron.xml): > {code} > /core-service=management/management-interface=native-interface:add(sasl-authentication-factory=application-sasl-authentication,security-realm=ApplicationRealm,socket-binding=management-http) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0105: sasl-authentication-factory is invalid in combination with security-realm", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2031) Update description of security-realm in management interfaces

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2031?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2031: ------------------------------------- Comment: was deleted (was: The PR description didn't include this in the list of fixed issues, but I think the commit in the pr was the fix.) > Update description of security-realm in management interfaces > ------------------------------------------------------------- > > Key: WFCORE-2031 > URL: https://issues.jboss.org/browse/WFCORE-2031 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > Fix For: 3.0.0.Alpha15 > > > Description of security-realm attribute in HTTP (and native) management interfaces says: > "The security realm to use for the HTTP management interface." or "The security realm to use for the native management interface." > However Elytron also uses security-realms. Description of mentioned about attribute should include information that it uses *legacy* security realm (not Elytron). Without word "legacy" it can be confusing since two different types of security-realm currently occur in configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1954) Wrap CLIENT_CERT behaviour of legacy realms with Elytron components.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1954?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1954: ------------------------------------- Fix Version/s: 3.0.0.Alpha15 (was: 3.0.0.Alpha16) > Wrap CLIENT_CERT behaviour of legacy realms with Elytron components. > -------------------------------------------------------------------- > > Key: WFCORE-1954 > URL: https://issues.jboss.org/browse/WFCORE-1954 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Alpha15 > > > An re-enable the following test: - > * org.jboss.as.test.integration.domain.HTTPSManagementInterfaceTestCase -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2027) Option server_config should be a file name not a path as stated by command help

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2027?page=com.atlassian.jira.plugi... ] Ken Wills closed WFCORE-2027. ----------------------------- Resolution: Duplicate Issue See WFCORE-1977 for the supported solution. > Option server_config should be a file name not a path as stated by command help > ------------------------------------------------------------------------------- > > Key: WFCORE-2027 > URL: https://issues.jboss.org/browse/WFCORE-2027 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > > embed-server --help, says the server_config should be the name of the file and not a path, you can set a path relative to the standalone/configuration that can be in any place inside the server ../../../ it does load the file you set there but then fails to change any properties as it does in the default standalone under jboss_home/standalone/config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 December 2016