February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6573: ----------------------------------- Comment: was deleted (was: Customer Allianz Managed Operations & Services SE would like this feature to be implemented.) > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Darran Lofthouse > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-907) LdapRealm - different principal/credential for referrals

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-907?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-907: --------------------------- Description: When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. This can be done when using AuthenticationContext. Note: how to pass different credentials into referred DirContext: http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) was: When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. This can be done using AuthenticationContext by following way: http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) > LdapRealm - different principal/credential for referrals > -------------------------------------------------------- > > Key: ELY-907 > URL: https://issues.jboss.org/browse/ELY-907 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. > This can be done when using AuthenticationContext. > Note: how to pass different credentials into referred DirContext: > http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-907) LdapRealm - different principal/credential for referrals

by Jan Kalina (JIRA)

Jan Kalina created ELY-907: ------------------------------ Summary: LdapRealm - different principal/credential for referrals Key: ELY-907 URL: https://issues.jboss.org/browse/ELY-907 Project: WildFly Elytron Issue Type: Enhancement Reporter: Jan Kalina Assignee: Jan Kalina Priority: Minor When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. This can be done using AuthenticationContext by following way: http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1425) QueryCepFireUntilHaltTest often hangs during execution

by Petr Široký (JIRA)

Petr Široký created DROOLS-1425: ----------------------------------- Summary: QueryCepFireUntilHaltTest often hangs during execution Key: DROOLS-1425 URL: https://issues.jboss.org/browse/DROOLS-1425 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.0.0.Beta6 Reporter: Petr Široký Assignee: Mario Fusco Attachments: QueryCepFireUntilHaltTest-thread-dump.txt The {{QueryCepFireUntilHaltTest}} recently started to hang the build quite often. It does use specific timeout, but either the timeout it too high (so the build timeouts anyway) or jUnit is not able to kill the test after the timeout passes. Based on the threaddump taken during the build, there seems to be a deadlock between two threads (see the attachment). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1425) QueryCepFireUntilHaltTest often hangs during execution

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1425?page=com.atlassian.jira.plugi... ] Petr Široký updated DROOLS-1425: -------------------------------- Attachment: QueryCepFireUntilHaltTest-thread-dump.txt > QueryCepFireUntilHaltTest often hangs during execution > ------------------------------------------------------ > > Key: DROOLS-1425 > URL: https://issues.jboss.org/browse/DROOLS-1425 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Petr Široký > Assignee: Mario Fusco > Attachments: QueryCepFireUntilHaltTest-thread-dump.txt > > > The {{QueryCepFireUntilHaltTest}} recently started to hang the build quite often. It does use specific timeout, but either the timeout it too high (so the build timeouts anyway) or jUnit is not able to kill the test after the timeout passes. Based on the threaddump taken during the build, there seems to be a deadlock between two threads (see the attachment). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2259) Setting JBOSS_MODULEPATH is lost for second start of embed-server

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2259?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos closed WFCORE-2259. ------------------------------------------- Resolution: Duplicate Issue > Setting JBOSS_MODULEPATH is lost for second start of embed-server > ----------------------------------------------------------------- > > Key: WFCORE-2259 > URL: https://issues.jboss.org/browse/WFCORE-2259 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Server > Reporter: Panagiotis Sotiropoulos > Assignee: Brian Stansberry > Priority: Critical > > When {{embed-server}} command is used more times in the CLI and a custom {{JBOSS_MODULEPATH}} is configured, then only the first server start uses the correct module path. > The subsequent `embed-server` call results in error: > {code} > Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0118: Determined modules directory does not exist: /tmp/jboss-eap-7.0-no-modules/modules > {code} > Using the {{JBOSS_MODULEPATH}} environment variable is documented in https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2259) Setting JBOSS_MODULEPATH is lost for second start of embed-server

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created WFCORE-2259: ----------------------------------------------- Summary: Setting JBOSS_MODULEPATH is lost for second start of embed-server Key: WFCORE-2259 URL: https://issues.jboss.org/browse/WFCORE-2259 Project: WildFly Core Issue Type: Bug Components: CLI, Server Reporter: Panagiotis Sotiropoulos Assignee: Brian Stansberry Priority: Critical Fix For: 3.0.0.Alpha23 When {{embed-server}} command is used more times in the CLI and a custom {{JBOSS_MODULEPATH}} is configured, then only the first server start uses the correct module path. The subsequent `embed-server` call results in error: {code} Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0118: Determined modules directory does not exist: /tmp/jboss-eap-7.0-no-modules/modules {code} Using the {{JBOSS_MODULEPATH}} environment variable is documented in https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2259) Setting JBOSS_MODULEPATH is lost for second start of embed-server

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2259?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos updated WFCORE-2259: -------------------------------------------- Fix Version/s: (was: 3.0.0.Alpha23) > Setting JBOSS_MODULEPATH is lost for second start of embed-server > ----------------------------------------------------------------- > > Key: WFCORE-2259 > URL: https://issues.jboss.org/browse/WFCORE-2259 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Server > Reporter: Panagiotis Sotiropoulos > Assignee: Brian Stansberry > Priority: Critical > > When {{embed-server}} command is used more times in the CLI and a custom {{JBOSS_MODULEPATH}} is configured, then only the first server start uses the correct module path. > The subsequent `embed-server` call results in error: > {code} > Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0118: Determined modules directory does not exist: /tmp/jboss-eap-7.0-no-modules/modules > {code} > Using the {{JBOSS_MODULEPATH}} environment variable is documented in https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Lei Yu (JIRA)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Lei Yu commented on WFLY-6573: ------------------------------ Customer Allianz Managed Operations & Services SE would like this feature to be implemented. > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Darran Lofthouse > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-901) Credential Store doesn't support set create.storage true/false

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-901?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek closed ELY-901. ---------------------------- Resolution: Duplicate Issue > Credential Store doesn't support set create.storage true/false > -------------------------------------------------------------- > > Key: ELY-901 > URL: https://issues.jboss.org/browse/ELY-901 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Peter Skopek > > Credential Store doesn't support set create.storage true/false. > Earlier we were able to set create.storage to true/false. > I can see problem in this scenario: > * I want to create new CS with path to existing CS file > * I fill wrong path > * Everything pass > But I want to use my CS file, not to create new one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017