Mo Zo created JBWEB-231:
---------------------------
Summary: Globally configure <context-param> for the whole JBoss.
Key: JBWEB-231
URL: https://issues.jboss.org/browse/JBWEB-231
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: JBossWeb-7.0.9.GA, JBossWeb-7.0.2.GA, JBossWeb-7.0.1.GA , JBossWeb-7.0.0.GA
Reporter: Mo Zo
Assignee: Remy Maucherat
Please provide a way to set and configure a <context-param> globally for all applications within a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR.
Now it is only possible to configure it per application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
application.xml contextRoot is ignored when war contains @WebService
--------------------------------------------------------------------
Key: AS7-2556
URL: https://issues.jboss.org/browse/AS7-2556
Project: Application Server 7
Issue Type: Bug
Components: Deployment, Web Services
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
Reporter: Alexandre Gattiker
Assignee: Thomas Diesler
See Steps to reproduce below.
When deploying the archetype without modification:
10:12:57,545 INFO [org.jboss.web] (MSC service thread 1-6) registering web context: /test1
When adding a @WebService annotated class to the WAR:
10:15:33,203 INFO [org.jboss.web] (MSC service thread 1-1) registering web context: /test1-web-0.0.1-SNAPSHOT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Mo Zo created JBWEB-229:
---------------------------
Summary: Globally configure error pages for the whole JBoss.
Key: JBWEB-229
URL: https://issues.jboss.org/browse/JBWEB-229
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: JBossWeb-7.0.9.GA, JBossWeb-7.0.2.GA, JBossWeb-7.0.1.GA , JBossWeb-7.0.0.GA
Reporter: Mo Zo
Assignee: Remy Maucherat
Globally configure error pages for the whole JBoss.
Please provide a way to set error pages globally for all applications within a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR.
Now it is only possible to configure it per application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Anil Saldhana created AS7-3419:
----------------------------------
Summary: JBossWeb::ssl element in connector settings should check for vaultified strings
Key: AS7-3419
URL: https://issues.jboss.org/browse/AS7-3419
Project: Application Server 7
Issue Type: Feature Request
Components: Web
Affects Versions: 7.1.0.CR1
Reporter: Anil Saldhana
Assignee: Jean-Frederic Clere
Fix For: 7.1.0.Final
Currently, the passwords in the ssl element of the connector settings are in clear text.
https://community.jboss.org/wiki/JBossAS7SecuringPasswords describes very simple ways of checking whether a string is of the vault format and invoking the vault to get the decrypted string value.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Heiko Braun created AS7-3441:
--------------------------------
Summary: Selection models with KeyProviders break form data binding
Key: AS7-3441
URL: https://issues.jboss.org/browse/AS7-3441
Project: Application Server 7
Issue Type: Bug
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: 7.2.0.Alpha1
See JPA Metrics > PersistenceUnitList.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Mo Zo created JBWEB-227:
---------------------------
Summary: Globally configure a Valve for the whole JBoss.
Key: JBWEB-227
URL: https://issues.jboss.org/browse/JBWEB-227
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: All
Reporter: Mo Zo
Assignee: Remy Maucherat
Please provide a way to set and configure a Valve globally for all applications within a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml and DMR.
Now it is only possible to configure it per application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/SASL-11?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated SASL-11:
---------------------------------
Fix Version/s: 1.0.1.CR1
(was: 1.0.0.GA)
> From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: SASL-11
> URL: https://issues.jboss.org/browse/SASL-11
> Project: JBoss SASL Provider
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.1.CR1
>
>
> By using space as the separator a single realm name that contains a space is split into two realms.
> Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/SASL-10?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated SASL-10:
---------------------------------
Fix Version/s: 1.0.1.CR1
(was: 1.0.0.GA)
> Pluggable nonce handling strategy
> ---------------------------------
>
> Key: SASL-10
> URL: https://issues.jboss.org/browse/SASL-10
> Project: JBoss SASL Provider
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.1.CR1
>
>
> Implement a pluggable nonce handling strategy.
> At the very least we need to be able to switch to using a SecureRandom instead of Random.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Darran Lofthouse created AS7-3604:
-------------------------------------
Summary: Release and upgrade org.jboss.sasl to GA
Key: AS7-3604
URL: https://issues.jboss.org/browse/AS7-3604
Project: Application Server 7
Issue Type: Task
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 7.1.0.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira