January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-893) Release WildFly Elytron 1.1.0.Beta21

by Darran Lofthouse (JIRA)

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

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7944) Distributed Elytron-based SSO implementation

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7944: ---------------------------------- Summary: Distributed Elytron-based SSO implementation Key: WFLY-7944 URL: https://issues.jboss.org/browse/WFLY-7944 Project: WildFly Issue Type: Feature Request Components: Security Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 Add support for Elytron-based SSO to Undertow Subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2227) Upgrade to WildFly Elytron 1.1.0.Beta21

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2227: ---------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta21 Key: WFCORE-2227 URL: https://issues.jboss.org/browse/WFCORE-2227 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha21 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7943) Support for Elytron-based SSO to Undertow Subsystem

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7943: ---------------------------------- Summary: Support for Elytron-based SSO to Undertow Subsystem Key: WFLY-7943 URL: https://issues.jboss.org/browse/WFLY-7943 Project: WildFly Issue Type: Feature Request Components: Security Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Pedro Igor Add support for Elytron-based SSO to Undertow Subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-893) Release WildFly Elytron 1.1.0.Beta21

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-893: ------------------------------------ Summary: Release WildFly Elytron 1.1.0.Beta21 Key: ELY-893 URL: https://issues.jboss.org/browse/ELY-893 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta21 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-892) Invalidate sso session only from node that started logout

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ELY-892?page=com.atlassian.jira.plugin.sy... ] Paul Ferraro reassigned ELY-892: -------------------------------- Assignee: Paul Ferraro (was: Pedro Igor) > Invalidate sso session only from node that started logout > --------------------------------------------------------- > > Key: ELY-892 > URL: https://issues.jboss.org/browse/ELY-892 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.1.0.Beta20 > Reporter: Pedro Igor > Assignee: Paul Ferraro > Fix For: 1.1.0.Beta21 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2145) Confusing transitions of ControlledProcessState

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2145?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2145: ------------------------------------------ I updated the description to reflect the downstream issue so it's clear what's expected here. > Confusing transitions of ControlledProcessState > ----------------------------------------------- > > Key: WFCORE-2145 > URL: https://issues.jboss.org/browse/WFCORE-2145 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Starting a server into normal mode emits these transitions for the process running state: > - starting -> suspended -> normal > Similarly when transitioning to admin-only mode: > - starting -> suspended -> admin-only > Stopping from normal mode: > - normal -> suspending -> suspended -> stopping > Starting into suspended mode emits: > - starting -> stopping -> stopped > (and the {{stopped}} state represents that the server is actually in {{suspended}} mode) > I find it confusing that: > - -During a normal start, it transitions through a state named {{suspended}} even though the server is not suspended.- _this is actually correct_ > - -During a stop, it is even more confusing, because it goes through one extra state - {{suspending}} which doesn't occur during start.- - _this is actually correct_ > - The state to represent a suspended server is named {{stopped}} and not {{suspended}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2145) Confusing transitions of ControlledProcessState

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2145?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2145: ------------------------------------- Description: Starting a server into normal mode emits these transitions for the process running state: - starting -> suspended -> normal Similarly when transitioning to admin-only mode: - starting -> suspended -> admin-only Stopping from normal mode: - normal -> suspending -> suspended -> stopping Starting into suspended mode emits: - starting -> stopping -> stopped (and the {{stopped}} state represents that the server is actually in {{suspended}} mode) I find it confusing that: - -During a normal start, it transitions through a state named {{suspended}} even though the server is not suspended.- _this is actually correct_ - -During a stop, it is even more confusing, because it goes through one extra state - {{suspending}} which doesn't occur during start.- - _this is actually correct_ - The state to represent a suspended server is named {{stopped}} and not {{suspended}}. was: Starting a server into normal mode emits these transitions for the process running state: - starting -> suspended -> normal Similarly when transitioning to admin-only mode: - starting -> suspended -> admin-only Stopping from normal mode: - normal -> suspending -> suspended -> stopping Starting into suspended mode emits: - starting -> stopping -> stopped (and the {{stopped}} state represents that the server is actually in {{suspended}} mode) I find it confusing that: - During a normal start, it transitions through a state named {{suspended}} even though the server is not suspended. - During a stop, it is even more confusing, because it goes through one extra state - {{suspending}} which doesn't occur during start. - The state to represent a suspended server is named {{stopped}} and not {{suspended}}. > Confusing transitions of ControlledProcessState > ----------------------------------------------- > > Key: WFCORE-2145 > URL: https://issues.jboss.org/browse/WFCORE-2145 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Starting a server into normal mode emits these transitions for the process running state: > - starting -> suspended -> normal > Similarly when transitioning to admin-only mode: > - starting -> suspended -> admin-only > Stopping from normal mode: > - normal -> suspending -> suspended -> stopping > Starting into suspended mode emits: > - starting -> stopping -> stopped > (and the {{stopped}} state represents that the server is actually in {{suspended}} mode) > I find it confusing that: > - -During a normal start, it transitions through a state named {{suspended}} even though the server is not suspended.- _this is actually correct_ > - -During a stop, it is even more confusing, because it goes through one extra state - {{suspending}} which doesn't occur during start.- - _this is actually correct_ > - The state to represent a suspended server is named {{stopped}} and not {{suspended}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-892) Invalidate sso session only from node that started logout

by Pedro Igor (JIRA)

Pedro Igor created ELY-892: ------------------------------ Summary: Invalidate sso session only from node that started logout Key: ELY-892 URL: https://issues.jboss.org/browse/ELY-892 Project: WildFly Elytron Issue Type: Bug Components: HTTP Affects Versions: 1.1.0.Beta20 Reporter: Pedro Igor Assignee: Pedro Igor Fix For: 1.1.0.Beta21 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-891) Cloning fixes in IdentityCredentials and RawClearPassword

by Farah Juma (JIRA)

Farah Juma created ELY-891: ------------------------------ Summary: Cloning fixes in IdentityCredentials and RawClearPassword Key: ELY-891 URL: https://issues.jboss.org/browse/ELY-891 Project: WildFly Elytron Issue Type: Bug Components: Passwords Reporter: Farah Juma Assignee: Farah Juma CredentialNode.getCredential() should clone the credential returned so that the destruction of any wrapped passwords does not affect the cached instance. RawClearPassword.clone() should clone the password array. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017