[JBoss JIRA] (ELY-261) Rework (and move) UsernamePasswordHashUtil
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-261?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-261:
---------------------------------
Fix Version/s: 1.1.0.CR7
(was: 1.1.0.CR6)
> Rework (and move) UsernamePasswordHashUtil
> ------------------------------------------
>
> Key: ELY-261
> URL: https://issues.jboss.org/browse/ELY-261
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI, Passwords
> Reporter: Darran Lofthouse
> Fix For: 1.1.0.CR7
>
>
> Firstly this class is not really SASL specific so should be in a general util package.
> Secondly we now have password specs and a PasswordFactory - if this class still has a future then maybe it should be using those instead of it's own custom implementation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1309) Channel binding callback cannot support tls-unique
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1309?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1309:
----------------------------------
Fix Version/s: 1.1.0.CR7
(was: 1.1.0.CR6)
> Channel binding callback cannot support tls-unique
> --------------------------------------------------
>
> Key: ELY-1309
> URL: https://issues.jboss.org/browse/ELY-1309
> Project: WildFly Elytron
> Issue Type: Bug
> Components: API / SPI, Authentication Client, Authentication Server, Callbacks, SASL
> Reporter: David Lloyd
> Assignee: David Lloyd
> Priority: Blocker
> Fix For: 1.1.0.CR7
>
>
> The revised API for the channel binding callback uses SSL sessions, but the standard TLS channel binding types [according to the RFC|https://tools.ietf.org/html/rfc5929] are associated with the connection, not the session. It is likely that the proposed channel bindings JDK API will exist on SSLSocket/SSLEngine. Introduce an API that allows the callback handlers to acquire the connection information using a forward-compatible API.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9237) Remarshaling the default configuration xml files shouldn't change the files
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFLY-9237:
---------------------------------------
Summary: Remarshaling the default configuration xml files shouldn't change the files
Key: WFLY-9237
URL: https://issues.jboss.org/browse/WFLY-9237
Project: WildFly
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 11.0.0.Beta1
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Starting a server and provoking a marshaling of the model without any real change on the default configuration files shouldn't result in a different files (with empty lines).
Reproducer:
* start the server or domain
* add and remove a system property using the CLI
* diff the resulting configuration file with the initial one.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9236) Remarshaling the default configuration xml files shouldn't change the files
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-9236?page=com.atlassian.jira.plugin.... ]
ehsavoie Hugonnet moved WFCORE-3194 to WFLY-9236:
-------------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-9236 (was: WFCORE-3194)
Component/s: Domain Management
(was: Domain Management)
Affects Version/s: 11.0.0.Beta1
(was: 3.0.0.Beta31)
> Remarshaling the default configuration xml files shouldn't change the files
> ---------------------------------------------------------------------------
>
> Key: WFLY-9236
> URL: https://issues.jboss.org/browse/WFLY-9236
> Project: WildFly
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 11.0.0.Beta1
> Reporter: ehsavoie Hugonnet
> Assignee: ehsavoie Hugonnet
>
> Starting a server and provoking a marshaling of the model without any real change on the default configuration files shouldn't result in a different files (with empty lines).
> Reproducer:
> * start the server or domain
> * add and remove a system property using the CLI
> * diff the resulting configuration file with the initial one.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months