[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
[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
[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
[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