[JBoss JIRA] (WFCORE-605) MORE_JAVA_OPTS for standalone.sh
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-605?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda commented on WFCORE-605:
------------------------------------------
What will happen with WILDFLY_EXTRA_JAVA_OPTS when it goes into the product ? EAP_EXTRA_JAVA_OPTS ?
Appending additional environment variables to the standalone.conf should be enough
{code}
echo "JAVA_OPTS=\"$JAVA_OPTS -Dkey.value\"" >> $JBOSS_HOME/standalone.conf
{code}
> MORE_JAVA_OPTS for standalone.sh
> --------------------------------
>
> Key: WFCORE-605
> URL: https://issues.jboss.org/browse/WFCORE-605
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Scripts
> Reporter: Arun Gupta
>
> Extend standalone.sh such that it takes an additional environment variable that is then added to JAVA_OPTS during startup.
> This can be used for passing additional Java options from WildFly
> Docker image. Cursory look at the script does not reveal anything like
> that exist.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4456) Set "module" element in the web console when creating security-domain login-module
by Carlton Zachary (JIRA)
[ https://issues.jboss.org/browse/WFLY-4456?page=com.atlassian.jira.plugin.... ]
Carlton Zachary updated WFLY-4456:
----------------------------------
Summary: Set "module" element in the web console when creating security-domain login-module (was: Set "module" attribute in the web console when creating security-domain login-module)
Description: Can the web console be updated to allow setting the value of the "module" element when creating a login-module in the "security-domain". This is possible via the CLI, just needs to be added to the console. (was: Can the web console be updated to allow setting the value of the "module" attribute when creating a login-module in the "security-domain". This is possible via the CLI, just needs to be added to the console.)
> Set "module" element in the web console when creating security-domain login-module
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4456
> URL: https://issues.jboss.org/browse/WFLY-4456
> Project: WildFly
> Issue Type: Enhancement
> Components: Web Console
> Affects Versions: 8.2.0.Final
> Reporter: Carlton Zachary
> Assignee: Heiko Braun
>
> Can the web console be updated to allow setting the value of the "module" element when creating a login-module in the "security-domain". This is possible via the CLI, just needs to be added to the console.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4456) Set "module" attribute in the web console when creating security-domain login-module
by Carlton Zachary (JIRA)
Carlton Zachary created WFLY-4456:
-------------------------------------
Summary: Set "module" attribute in the web console when creating security-domain login-module
Key: WFLY-4456
URL: https://issues.jboss.org/browse/WFLY-4456
Project: WildFly
Issue Type: Enhancement
Components: Web Console
Affects Versions: 8.2.0.Final
Reporter: Carlton Zachary
Assignee: Heiko Braun
Can the web console be updated to allow setting the value of the "module" attribute when creating a login-module in the "security-domain". This is possible via the CLI, just needs to be added to the console.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-3901) Please add the "relative-to" attribute to access-log in undertow
by Carlton Zachary (JIRA)
[ https://issues.jboss.org/browse/WFLY-3901?page=com.atlassian.jira.plugin.... ]
Carlton Zachary commented on WFLY-3901:
---------------------------------------
Is there any movement on this?
Thanks
> Please add the "relative-to" attribute to access-log in undertow
> ----------------------------------------------------------------
>
> Key: WFLY-3901
> URL: https://issues.jboss.org/browse/WFLY-3901
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Carlton Zachary
> Assignee: Tomaz Cerar
>
> I have been trying to point the "directory" attribute value to a var ${custom.jboss.server.log.dir} to write the access.log to a non-default location, but this diesn't work in undertow. It does work in EAP 6.2 JBoss-web. The custom.jboss.server.log.dir is defined in the "<paths>" in the servers section of the host-slave.xml file.
> In JBoss EAP 6.2 with jboss-web the access-log has the "relative-to" attribute, but this is not the case with access-log for undertow in WFLY 8.1.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBASMP-76) Start goal occasionally end prematurely on standalone server
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-76?page=com.atlassian.jira.plugin.... ]
James Perkins commented on JBASMP-76:
-------------------------------------
Sure enough it's lowercase. I guess that's definitely a bug.
> Start goal occasionally end prematurely on standalone server
> ------------------------------------------------------------
>
> Key: JBASMP-76
> URL: https://issues.jboss.org/browse/JBASMP-76
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Affects Versions: 7.7.Final
> Environment: JBoss AS 7.2.0
> Reporter: Daniele Gaffuri
> Assignee: James Perkins
> Attachments: patch.diff
>
>
> When server startup time is over 10 seconds start goal ends prematurely, because test on server-state property checks "starting" and "stopping" states in wrong case (constants are defined in uppercase but are retured in lowercase by client call)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBASMP-76) Start goal occasionally end prematurely on standalone server
by Daniele Gaffuri (JIRA)
[ https://issues.jboss.org/browse/JBASMP-76?page=com.atlassian.jira.plugin.... ]
Daniele Gaffuri commented on JBASMP-76:
---------------------------------------
It's the first thing I've tried, with no result. Then I've added a debug print in StandaloneServer.checkServerState()
{code}
isRunning = ServerOperations.isSuccessfulOutcome(result) && !STARTING.equalsIgnoreCase(ServerOperations.readResultAsString(result)) &&
!STOPPING.equalsIgnoreCase(ServerOperations.readResultAsString(result));
System.out.println("******************** result is " + ServerOperations.readResultAsString(result));
{code}
and I saw the result returned in lowercase and the start goal returning immediately after the first log
{code}
[INFO] Server is starting up.
Mar 23, 2015 6:14:38 PM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.7.GA
Mar 23, 2015 6:14:38 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.7.GA
Mar 23, 2015 6:14:38 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.12.GA
.........
18:14:49,793 INFO [org.hornetq.core.server] (MSC service thread 1-4) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5445 for CORE protocol
18:14:49,817 INFO [org.hornetq.core.server] (MSC service thread 1-4) HQ221024: Started Netty Acceptor version 3.6.2.Final-c0d783c 127.0.0.1:5455 for CORE protocol
18:14:49,819 INFO [org.hornetq.core.server] (MSC service thread 1-4) HQ221009: Server is now live
18:14:49,823 INFO [org.hornetq.core.server] (MSC service thread 1-4) HQ221003: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [09dc3be1-cfac-11e4-82ac-5dac6ad5d88b]
******************** result is starting
[INFO]
.........
{code}
> Start goal occasionally end prematurely on standalone server
> ------------------------------------------------------------
>
> Key: JBASMP-76
> URL: https://issues.jboss.org/browse/JBASMP-76
> Project: JBoss AS Maven Plugins
> Issue Type: Bug
> Affects Versions: 7.7.Final
> Environment: JBoss AS 7.2.0
> Reporter: Daniele Gaffuri
> Assignee: James Perkins
> Attachments: patch.diff
>
>
> When server startup time is over 10 seconds start goal ends prematurely, because test on server-state property checks "starting" and "stopping" states in wrong case (constants are defined in uppercase but are retured in lowercase by client call)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (SECURITY-877) WildFLy is Logging LDAP Bind Credential Password for SPNEGO code
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/SECURITY-877?page=com.atlassian.jira.plug... ]
Filippe Spolti commented on SECURITY-877:
-----------------------------------------
Tested:
09:09:06,416 TRACE [org.jboss.security.auth.spi.AbstractServerLoginModule] (http-/0.0.0.0:8080-1) Logging into LDAP server, env={java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, roleNameAttributeID=cn, java.naming.security.principal=test, password-stacking=useFirstPass, baseCtxDN=CN=Users,DC=jbossuk,DC=com, java.naming.ldap.attributes.binary=objectSid, roleAttributeID=memberOf, baseFilter=(sAMAccountName={0}), jboss.security.security_domain=SPNEGO, java.naming.provider.url=ldap://localhost:389, allowEmptyPassword=true, roleAttributeIsDN=true, bindDN=test, bindCredential=***, java.naming.security.authentication=simple, recurseRoles=true, java.naming.security.credentials=***}
> WildFLy is Logging LDAP Bind Credential Password for SPNEGO code
> ----------------------------------------------------------------
>
> Key: SECURITY-877
> URL: https://issues.jboss.org/browse/SECURITY-877
> Project: PicketBox
> Issue Type: Bug
> Components: Negotiation
> Affects Versions: Negotiation_2_3_6_Final
> Environment: Wildfly is logging the bindCredentials when using SPNEGO
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Minor
>
> The bind Credential are being logged:
> 2015-03-19 19:33:28,569 TRACE [org.jboss.security.auth.spi.AbstractServerLoginModule] (http-localhost/127.0.0.1:8080-1) Logging into LDAP server, env={baseFilter=(userPrincipalName={0}), java.naming.security.credentials=***, jboss.security.security_domain=SPNEGO, java.naming.ldap.attributes.binary=objectSid, password-stacking=useFirstPass, recurseRoles=false, java.naming.security.authentication=simple, baseCtxDN=DC=example,DC=com, roleAttributeIsDN=true, rolesCtxDN=DC=example,DC=com, java.naming.security.principal=bindUser, allowEmptyPassword=true, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.provider.url=ldap://127.0.0.1:389, roleNameAttributeID=cn, roleAttributeID=memberOf, bindDN=bindUser, bindCredential=password}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months