February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-931) Release WildFly Elytron 1.1.0.Beta23

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-931?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-931. ---------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta23 > ------------------------------------ > > Key: ELY-931 > URL: https://issues.jboss.org/browse/ELY-931 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta23 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-925) Update SecurityDomain to allow association with and retrieval from ClassLoader

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-925?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-925. ---------------------------------- Resolution: Done > Update SecurityDomain to allow association with and retrieval from ClassLoader > ------------------------------------------------------------------------------ > > Key: ELY-925 > URL: https://issues.jboss.org/browse/ELY-925 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta23 > > > Get, Set, and Unset should all be backed by SecurityManager permissions. > We may relax the permission assigned to Get once we have double checked sufficient permission checks on the SecurityDomain and SecurityIdentity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8052) Upgrade to Elytron Subsystem 1.0.0.Beta5

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-8052: -------------------------------------- Summary: Upgrade to Elytron Subsystem 1.0.0.Beta5 Key: WFLY-8052 URL: https://issues.jboss.org/browse/WFLY-8052 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8051) Backport latest Elytron Integration changes

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8051?page=com.atlassian.jira.plugin.... ] Darran Lofthouse moved WFCORE-2277 to WFLY-8051: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-8051 (was: WFCORE-2277) Component/s: Security (was: Security) Fix Version/s: 11.0.0.Alpha1 (was: 3.0.0.Alpha24) > Backport latest Elytron Integration changes > ------------------------------------------- > > Key: WFLY-8051 > URL: https://issues.jboss.org/browse/WFLY-8051 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2276) Backport latest Elytron Integration changes

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2276: ---------------------------------------- Summary: Backport latest Elytron Integration changes Key: WFCORE-2276 URL: https://issues.jboss.org/browse/WFCORE-2276 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha24 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2277) Backport latest Elytron Integration changes

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2277: ---------------------------------------- Summary: Backport latest Elytron Integration changes Key: WFCORE-2277 URL: https://issues.jboss.org/browse/WFCORE-2277 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha24 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7996) Default Elytron subsystem configuration doesn't support local authentication in ApplicationRealm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7996?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7996: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Default Elytron subsystem configuration doesn't support local authentication in ApplicationRealm > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7996 > URL: https://issues.jboss.org/browse/WFLY-7996 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Jan Kalina > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > The default Elytron configuration in profiles doesn't configure {{JBOSS-LOCAL-USER}} SASL mechanism for ApplicationRealm. If a client (e.g JMS/naming) uses local authentication in legacy security, it will not work after switching to Elytron based security. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7653) Validate session-timeout and maximum-session-cache-size to be non-negative

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7653?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7653: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Validate session-timeout and maximum-session-cache-size to be non-negative > -------------------------------------------------------------------------- > > Key: WFLY-7653 > URL: https://issues.jboss.org/browse/WFLY-7653 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Negative values are invalid in this case because they do not make sense for these attributes. Also java throws IllegalArgumentException, when they get negative values on that place. [1] > Please add validation to limit these values to zero and positive values in: > * model > * XSD > That applies for both: > * client-ssl-context > * server-ssl-context > [1] http://www.ibm.com/support/knowledgecenter/SSVHEW_6.2.0/com.ibm.rcp.dee.j... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7977) Synchronize XSD and DMR description of obtain-kerberos-ticket attribute

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7977?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7977: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Synchronize XSD and DMR description of obtain-kerberos-ticket attribute > ----------------------------------------------------------------------- > > Key: WFLY-7977 > URL: https://issues.jboss.org/browse/WFLY-7977 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Add this sentence "This is required to be true where credentials are delegated to the server." to description of obtain-kerberos-ticket attribute. > {code:Management Model} > "obtain-kerberos-ticket" => { > "type" => BOOLEAN, > "description" => "Should the KerberosTicket also be obtained and associated with the credential.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > As already is in XSD > {code:xml|title=wildfly-elytron.xsd} > <xs:attribute name="obtain-kerberos-ticket" type="xs:boolean" default="false"> > <xs:annotation> > <xs:documentation> > Should the KerberosTicket also be obtained and associated with the credential. > This is required to be true where credentials are delegated to the server. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7977) Synchronize XSD and DMR description of obtain-kerberos-ticket attribute

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7977?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7977: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > Synchronize XSD and DMR description of obtain-kerberos-ticket attribute > ----------------------------------------------------------------------- > > Key: WFLY-7977 > URL: https://issues.jboss.org/browse/WFLY-7977 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Ilia Vassilev > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > Add this sentence "This is required to be true where credentials are delegated to the server." to description of obtain-kerberos-ticket attribute. > {code:Management Model} > "obtain-kerberos-ticket" => { > "type" => BOOLEAN, > "description" => "Should the KerberosTicket also be obtained and associated with the credential.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > As already is in XSD > {code:xml|title=wildfly-elytron.xsd} > <xs:attribute name="obtain-kerberos-ticket" type="xs:boolean" default="false"> > <xs:annotation> > <xs:documentation> > Should the KerberosTicket also be obtained and associated with the credential. > This is required to be true where credentials are delegated to the server. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {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