[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-4238:
----------------------------------------
[~abha.kashid] If you want to have a discussion please take this to the forums, the shared key is no longer a required field so is not required in the config files hence this being a documentation issue.
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Peter Skopek
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1905?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1905 at 1/12/15 4:41 AM:
---------------------------------------------------------
Hi Paul,
I looked at this, but don't see a way to fix this in JGroups (it can be fixed in WildFly/Infinispan though... read on).
I cannot send a fork-channel=not-available exception or flag back to the RPC caller as the request message hasn't reached the RequestCorrelator/RpcDispatcher code, so at this point JGroups doesn't know anything about RPCs yet.
However, you could create (and connect) the fork-channel "web" *before* connecting the main-chanel "ee", so the code would not throw an NPE:
{code}
JChannel ee=new JChannel(...);
ForkChannel web=new ForkChannel(ee, "stack", "web");
web.connect("bla"); // <-- fork-channel will get connected when main-channel connects (below)
ee.connect("bla");
{code}
Take a look at [1] for sample code.
[1] https://github.com/belaban/JGroups/blob/master/tests/junit-functional/org...
was (Author: belaban):
Hi Paul,
I looked at this, but don't see a way to fix this in JGroups (it can be fixed in WildFly/Infinispan though... read on).
I cannot send a fork-channel=not-available exception or flag back to the RPC caller as the request message hasn't reached the RequestCorrelator/RpcDispatcher code, so at this point JGroups doesn't know anything about RPCs yet.
However, you could create (and connect) the fork-channel "web" *before* connecting the main-chanel "ee", so the code would not throw an NPE:
{code}
JChannel ee=new JChannel(...);
ForkChannel web=new ForkChannel(ee, "stack", "web");
web.connect("bla");
ee.connect*"bla");
{code}
Take a look at [1] for sample code.
[1] https://github.com/belaban/JGroups/blob/master/tests/junit-functional/org...
> FORK: RPCs might block if fork channel or fork stack is not available
> ---------------------------------------------------------------------
>
> Key: JGRP-1905
> URL: https://issues.jboss.org/browse/JGRP-1905
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Critical
> Fix For: 3.6.2
>
>
> When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out.
> h5. Solution
> * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available").
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Abhinav Gupta (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Abhinav Gupta commented on WFLY-4238:
-------------------------------------
Just to add , it does'nt sound like this is only from documentation perspective. Shared key should be print on console , as user need to copy that and put it in config files.
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Peter Skopek
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1905?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1905 at 1/12/15 4:39 AM:
---------------------------------------------------------
Hi Paul,
I looked at this, but don't see a way to fix this in JGroups (it can be fixed in WildFly/Infinispan though... read on).
I cannot send a fork-channel=not-available exception or flag back to the RPC caller as the request message hasn't reached the RequestCorrelator/RpcDispatcher code, so at this point JGroups doesn't know anything about RPCs yet.
However, you could create (and connect) the fork-channel "web" *before* connecting the main-chanel "ee", so the code would not throw an NPE:
{code}
JChannel ee=new JChannel(...);
ForkChannel web=new ForkChannel(ee, "stack", "web");
web.connect("bla");
ee.connect*"bla");
{code}
Take a look at [1] for sample code.
[1] https://github.com/belaban/JGroups/blob/master/tests/junit-functional/org...
was (Author: belaban):
Hi Paul,
I looked at this, but don't see a way to fix this in JGroups (it can be fixed in WildFly/Infinispan though... read on).
I cannot send a fork-channel=not-available exception or flag back to the RPC caller as the request message hasn't reached the RequestCorrelator/RpcDispatcher code, so at this point JGroups doesn't know anything about RPCs yet.
However, you could create (and connect) the fork-channel "web" *before* connecting the main-chanel "ee", so the code would not throw an NPE:
{code}
JChannel ee=new JChannel(...);
ForkChannel web=new ForkChannel(ee, "stack", "web");
web.connect("bla");
ee.connect*"bla");
{code}
> FORK: RPCs might block if fork channel or fork stack is not available
> ---------------------------------------------------------------------
>
> Key: JGRP-1905
> URL: https://issues.jboss.org/browse/JGRP-1905
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Critical
> Fix For: 3.6.2
>
>
> When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out.
> h5. Solution
> * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available").
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1905?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1905:
--------------------------------
Hi Paul,
I looked at this, but don't see a way to fix this in JGroups (it can be fixed in WildFly/Infinispan though... read on).
I cannot send a fork-channel=not-available exception or flag back to the RPC caller as the request message hasn't reached the RequestCorrelator/RpcDispatcher code, so at this point JGroups doesn't know anything about RPCs yet.
However, you could create (and connect) the fork-channel "web" *before* connecting the main-chanel "ee", so the code would not throw an NPE:
{code}
JChannel ee=new JChannel(...);
ForkChannel web=new ForkChannel(ee, "stack", "web");
web.connect("bla");
ee.connect*"bla");
{code}
> FORK: RPCs might block if fork channel or fork stack is not available
> ---------------------------------------------------------------------
>
> Key: JGRP-1905
> URL: https://issues.jboss.org/browse/JGRP-1905
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Critical
> Fix For: 3.6.2
>
>
> When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out.
> h5. Solution
> * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available").
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Abhinav Gupta (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Abhinav Gupta commented on WFLY-4238:
-------------------------------------
Hi Darran, Staurt,
Please have a look at below piece.. THis is what I get after try to save one password to vault.
I am expecting a Shared key in return .. But actual key is return as "VAULT::test1::pas::1" . Reason is I need a shared key to put in standalone.xml.
********************************************
Vault Block:test1
Attribute Name:pas
Configuration should be done as follows:
VAULT::test1::pas::1
********************************************
Let me know if I am still not clear in explaining.
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Peter Skopek
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-4238:
--------------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
Peter, just passing your way - doesn't sound like a bug as the format of the String has been changed but maybe worth double checking the referenced doc and either duplicate it and create a link for WF 8 or make that doc applicable for both 7 and 8.
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Peter Skopek
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4238?page=com.atlassian.jira.plugin.... ]
Stuart Douglas reassigned WFLY-4238:
------------------------------------
Assignee: Darran Lofthouse (was: Stuart Douglas)
Component/s: Security
(was: Application Client)
I'm not really sure what you mean? Do you mean that the characters don't show up as you type them?
> Vault script not showing shared key
> -----------------------------------
>
> Key: WFLY-4238
> URL: https://issues.jboss.org/browse/WFLY-4238
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 8.1.0.Final
> Environment: Windows 7 with jdk1.7.0_51
> Reporter: Abhinav Gupta
> Assignee: Darran Lofthouse
>
> Team,
> while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
> Below is console for vault.bat
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
> D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
> =========================================================================
> JBoss Vault Tool
> JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
> JAVA: "C:\jdk1.7.0_51\bin\java"
> JAVA_OPTS: ""
> =========================================================================
> **********************************
> **** JBoss Vault ***************
> **********************************
> Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
> 0
> Starting an interactive session
> Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
> Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
> Enter Keystore password:
> Enter Keystore password again:
> Values match
> Enter 8 character salt:12345678
> Enter iteration count as a number (e.g.: 44):50
> Enter Keystore Alias:vault
> Initializing Vault
> Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
> INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
> Vault Configuration in WildFly configuration file:
> ********************************************
> ...
> </extensions>
> <vault>
> <vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
> <vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
> <vault-option name="KEYSTORE_ALIAS" value="vault"/>
> <vault-option name="SALT" value="12345678"/>
> <vault-option name="ITERATION_COUNT" value="50"/>
> <vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
> </vault><management> ...
> ********************************************
> Vault is initialized and ready for use
> Handshake with Vault complete
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
> 0
> Task: Store a secured attribute
> Please enter secured attribute value (such as password):
> Please enter secured attribute value (such as password) again:
> Values match
> Enter Vault Block:test1
> Enter Attribute Name:pas
> Secured attribute value has been stored in Vault.
> Please make note of the following:
> ********************************************
> Vault Block:test1
> Attribute Name:pas
> Configuration should be done as follows:
> VAULT::test1::pas::1
> ********************************************
> Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFCORE-495) WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
by Chao Wang (JIRA)
Chao Wang created WFCORE-495:
--------------------------------
Summary: WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
Key: WFCORE-495
URL: https://issues.jboss.org/browse/WFCORE-495
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 1.0.0.Alpha15
Reporter: Chao Wang
Assignee: Chao Wang
WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
If you firstly deploy a .war application by CLI command, then deploy 2nd time same .war application by copying it to /depolyment directory. After server restart, it shows:
{noformat}
15:26:26,913 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) starting
15:26:27,133 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "xxx.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"
15:26:27,136 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:26:27,138 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
15:26:27,153 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha15) stopped in 4ms
{noformat}
steps to reproduce:
1. start wildfly and deploy a .war application by CLI.
2. copy same .war application to /deployment directory
3. restart wildfly to see the error message.
This happens because step 2 does a "full-replace-deployment" operation which does not remove content from standalone/data/content/aa/2d0425dd53572294d591b56efdee2680539eaf/content and deployment info from configuration file(standalone.xml). Therefore, you will have xxx.war in standalone/data/content and configuration file(standalone.xml), also a xxx.war and xxx.war.deployed file inside /standalone/deployments. A second time server restart will cause a duplicate resource error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months
[JBoss JIRA] (WFLY-4238) Vault script not showing shared key
by Abhinav Gupta (JIRA)
Abhinav Gupta created WFLY-4238:
-----------------------------------
Summary: Vault script not showing shared key
Key: WFLY-4238
URL: https://issues.jboss.org/browse/WFLY-4238
Project: WildFly
Issue Type: Bug
Components: Application Client
Affects Versions: 8.1.0.Final
Environment: Windows 7 with jdk1.7.0_51
Reporter: Abhinav Gupta
Assignee: Stuart Douglas
Team,
while using vault.bat , we are not able to see shared key. For every password entered I get a key as : VAULT::test1::pas::1
Below is console for vault.bat
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\bin>vault.bat
=========================================================================
JBoss Vault Tool
JBOSS_HOME: "D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly"
JAVA: "C:\jdk1.7.0_51\bin\java"
JAVA_OPTS: ""
=========================================================================
**********************************
**** JBoss Vault ***************
**********************************
Please enter a Digit:: 0: Start Interactive Session 1: Remove Interactive Session 2: Exit
0
Starting an interactive session
Enter directory to store encrypted files:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault
Enter Keystore URL:D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore
Enter Keystore password:
Enter Keystore password again:
Values match
Enter 8 character salt:12345678
Enter iteration count as a number (e.g.: 44):50
Enter Keystore Alias:vault
Initializing Vault
Jan 12, 2015 1:03:22 PM org.picketbox.plugins.vault.PicketBoxSecurityVault init
INFO: PBOX000361: Default Security Vault Implementation Initialized and Ready
Vault Configuration in WildFly configuration file:
********************************************
...
</extensions>
<vault>
<vault-option name="KEYSTORE_URL" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\vault.keystore"/>
<vault-option name="KEYSTORE_PASSWORD" value="MASK-InRT5Cuu6V"/>
<vault-option name="KEYSTORE_ALIAS" value="vault"/>
<vault-option name="SALT" value="12345678"/>
<vault-option name="ITERATION_COUNT" value="50"/>
<vault-option name="ENC_FILE_DIR" value="D:\e3c\E3C_Install_ZipTask_SCE_B3\sw\System\WildFly\vault\"/>
</vault><management> ...
********************************************
Vault is initialized and ready for use
Handshake with Vault complete
Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
0
Task: Store a secured attribute
Please enter secured attribute value (such as password):
Please enter secured attribute value (such as password) again:
Values match
Enter Vault Block:test1
Enter Attribute Name:pas
Secured attribute value has been stored in Vault.
Please make note of the following:
********************************************
Vault Block:test1
Attribute Name:pas
Configuration should be done as follows:
VAULT::test1::pas::1
********************************************
Please enter a Digit:: 0: Store a secured attribute 1: Check whether a secured attribute exists 2: Exit
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 6 months