[JBoss JIRA] (WFCORE-42) Add a ServerXml Parser which extends CommonXml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-42?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-42:
-----------------------------------
Fix Version/s: 1.0.0.Alpha12
(was: 1.0.0.Alpha11)
> Add a ServerXml Parser which extends CommonXml
> ----------------------------------------------
>
> Key: WFCORE-42
> URL: https://issues.jboss.org/browse/WFCORE-42
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha12
>
>
> Both StandaloneXml and AppclientXml parse XML starting from the server element.
> This duplication has always been problematic as AppclientXml is completely separate from the remaining domain config parsing, however with the core split this is even worse.
> This change is to introduce a ServerXml that can be the common base for both StandaloneXml and AppclientXml - except in extreme cases it will then be safe to ignore AppclientXml for further schema updates.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFCORE-94) Add -secmgr to startup scripts and propagate -secmgr through the domain
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-94?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-94:
-----------------------------------
Fix Version/s: 1.0.0.Alpha12
(was: 1.0.0.Alpha11)
> Add -secmgr to startup scripts and propagate -secmgr through the domain
> -----------------------------------------------------------------------
>
> Key: WFCORE-94
> URL: https://issues.jboss.org/browse/WFCORE-94
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management, Scripts
> Reporter: Kabir Khan
> Assignee: James Perkins
> Fix For: 1.0.0.Alpha12
>
>
> The preferred mechanism to enable a security manager is to use the -secmgr module option. Modify the scripts to make this easier to add, and make adjustments to propagate this through the domain.
> The -secmgr module option is not visible from the launched process, so for the process controller and host controller to pass that on to the started host controller or server process respectively, a check is added to see if a security manager was enabeld. If a security manager is enabled, and -Djava.security.manager is not present in the system properties, we add the -secmgr module option when starting the next process.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (WFCORE-77) We need even better reporting for failed authentications
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-77?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFCORE-77:
-----------------------------------
Fix Version/s: 1.0.0.Alpha12
(was: 1.0.0.Alpha11)
> We need even better reporting for failed authentications
> --------------------------------------------------------
>
> Key: WFCORE-77
> URL: https://issues.jboss.org/browse/WFCORE-77
> Project: WildFly Core
> Issue Type: Bug
> Components: Remoting
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha12
>
>
> The following message is often the one reported to users: -
> {noformat}
> >> Caused by: javax.security.sasl.SaslException: Authentication failed:
> >> the server presented no authentication mechanisms
> {noformat}
> Whilst technically it is true at that point in time this is most likely caused because other mechanisms have already been tried and failed and the list of mechanisms to try is now exhausted.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months