[JBoss JIRA] (WFCORE-2619) Unclear model description of core-pool-size attribute in IO subsystem
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2619?page=com.atlassian.jira.plugi... ]
Romain Pelisse updated WFCORE-2619:
-----------------------------------
Description:
*/subsystem=io/worker=\*:read-attribute(name=core-pool-size)*
Current model description: "Core worker thread pool size"
Suggested improvement: "Minimum number of threads to keep in the underlying java.util.concurrent.ThreadPoolExecutor even if they are idle. Threads over this limit will be terminated over time specified by task-keepalive attribute."
was:
*/subsystem=io/worker=*:read-attribute(name=core-pool-size)*
Current model description: "Core worker thread pool size"
Suggested improvement: "Minimum number of threads to keep in the underlying java.util.concurrent.ThreadPoolExecutor even if they are idle. Threads over this limit will be terminated over time specified by task-keepalive attribute."
> Unclear model description of core-pool-size attribute in IO subsystem
> ---------------------------------------------------------------------
>
> Key: WFCORE-2619
> URL: https://issues.jboss.org/browse/WFCORE-2619
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Affects Versions: 3.0.0.Beta12
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Minor
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> */subsystem=io/worker=\*:read-attribute(name=core-pool-size)*
> Current model description: "Core worker thread pool size"
> Suggested improvement: "Minimum number of threads to keep in the underlying java.util.concurrent.ThreadPoolExecutor even if they are idle. Threads over this limit will be terminated over time specified by task-keepalive attribute."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ELY-1027) CS tool, Parameter --salt requires --iteration and vice versa
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-1027?page=com.atlassian.jira.plugin.s... ]
Hynek Švábek updated ELY-1027:
------------------------------
Component/s: Credential Store
(was: Command-Line Tool)
> CS tool, Parameter --salt requires --iteration and vice versa
> -------------------------------------------------------------
>
> Key: ELY-1027
> URL: https://issues.jboss.org/browse/ELY-1027
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Assignee: Ilia Vassilev
>
> If I use only one parameter from --salt or --iteration then this one is ignored and result password is in clear text.
> {code}
> java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary --salt="abcdefgh"
> {code}
> Result of this command is:
> {code}
> Alias "myalias" has been successfully stored
> Credential store command summary:
> --------------------------------------
> /subsystem=elytron/credential-store=test:add(uri="cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="mycspassword"})
> {code}
> *There is expected error.*
> Please add there this constraint: parameter --salt requires --iteration and vice versa
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ELY-1047) CS tool, meaningless error msg when I create credential store storage file under OracleJDK and access to it under IBMJDK.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-1047?page=com.atlassian.jira.plugin.s... ]
Hynek Švábek updated ELY-1047:
------------------------------
Component/s: Credential Store
(was: Command-Line Tool)
> CS tool, meaningless error msg when I create credential store storage file under OracleJDK and access to it under IBMJDK.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1047
> URL: https://issues.jboss.org/browse/ELY-1047
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Assignee: Ilia Vassilev
>
> When I create credential store storage file under OracleJDK or OpenJDK and then I want to access to it under IBMJDK I get meaningless error message about this.
> I expect some error message about that you must use to access same JDK as was used for creation storage file.
> *How to reproduce*
> Create credential store storage file with OracleJDK (or openJDK)
> {code}
> java -jar wildfly-elytron-tool.jar credential-store --add moje --secret asdfasdf --location="PATH/TO/store01.jceks" --uri "cr-store://store01.jceks?modifiable=true;create=true;keyStoreType=JCEKS" --password=pass123 --summary
> {code}
> Try to list aliases with IBMJDK
> {code}
> java -jar wildfly-elytron-tool.jar credential-store --aliases --location="/PATH/TO/store01.jceks" --uri "cr-store://store01.jceks?modifiable=true;create=true;keyStoreType=JCEKS" --password=pass123 --summary
> ELY09526: Unable to initialize credential store
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-2619) Unclear model description of core-pool-size attribute in IO subsystem
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2619?page=com.atlassian.jira.plugi... ]
Romain Pelisse moved WFLY-8496 to WFCORE-2619:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2619 (was: WFLY-8496)
Component/s: IO
(was: IO)
Affects Version/s: 3.0.0.Beta12
(was: 11.0.0.Alpha1)
> Unclear model description of core-pool-size attribute in IO subsystem
> ---------------------------------------------------------------------
>
> Key: WFCORE-2619
> URL: https://issues.jboss.org/browse/WFCORE-2619
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Affects Versions: 3.0.0.Beta12
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Minor
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> */subsystem=io/worker=*:read-attribute(name=core-pool-size)*
> Current model description: "Core worker thread pool size"
> Suggested improvement: "Minimum number of threads to keep in the underlying java.util.concurrent.ThreadPoolExecutor even if they are idle. Threads over this limit will be terminated over time specified by task-keepalive attribute."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-2618) CS tool, Without --location parameter a credential store storage file isn't saved (or save as is expected).
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2618?page=com.atlassian.jira.plugi... ]
Hynek Švábek commented on WFCORE-2618:
--------------------------------------
[~ivassile]
Wildfly-elytron-tool is located in wildfly-elytron project -> ELY project is right for this issue.
> CS tool, Without --location parameter a credential store storage file isn't saved (or save as is expected).
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2618
> URL: https://issues.jboss.org/browse/WFCORE-2618
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta11
> Reporter: Hynek Švábek
> Assignee: Ilia Vassilev
>
> Without --location parameter a credential store storage file isn't saved (or save as is expected).
> It pass but I am not able find credential store storage file on disk.
> {code}
> [hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --uri "cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary
> Alias "myalias" has been successfully stored
> Credential store command summary:
> --------------------------------------
> /subsystem=elytron/credential-store=test:add(uri="cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="mycspassword"})
> {code}
> It pass with this URI value and I am able to find credential store storage file on disk.
> {code}
> uri="cr-store://credentialstorename/test.store?modifiable=true;create=true;keyStoreType=JCEKS"
> {code}
> I see problem here https://github.com/wildfly-security/wildfly-elytron-tool/blob/1.0.0.Alpha...
> (test.store is interpreded as hostname in URI in first case)
> *NOTE*
> Please keep in mind this issue https://issues.jboss.org/browse/JBEAP-8450.
> Behaviour must be consistent!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ELY-1053) Review realm attribute in Elytron authentication-configuration
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1053?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1053:
------------------------------
Affects Version/s: 1.1.0.Beta31-SP1
> Review realm attribute in Elytron authentication-configuration
> --------------------------------------------------------------
>
> Key: ELY-1053
> URL: https://issues.jboss.org/browse/ELY-1053
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta31-SP1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
>
> Is there any real scenario for usage of {{realm}} attribute in authentication-configuration?
> If server provides DIGEST-MD5 mechanism and client chooses it, then server provides name of realm which should be used for creating {{user:realm:password}} digest. It was the original reason which was provided to us. However it seems that reason for that attribute is currently different. What is the reason for attribute {{realm}} in authentication-configuration?
> This information will be also needed for documentation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ELY-1053) Review realm attribute in Elytron authentication-configuration
by Ondrej Lukas (JIRA)
Ondrej Lukas created ELY-1053:
---------------------------------
Summary: Review realm attribute in Elytron authentication-configuration
Key: ELY-1053
URL: https://issues.jboss.org/browse/ELY-1053
Project: WildFly Elytron
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
Is there any real scenario for usage of {{realm}} attribute in authentication-configuration?
If server provides DIGEST-MD5 mechanism and client chooses it, then server provides name of realm which should be used for creating {{user:realm:password}} digest. It was the original reason which was provided to us. However it seems that reason for that attribute is currently different. What is the reason for attribute {{realm}} in authentication-configuration?
This information will be also needed for documentation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months