[JBoss JIRA] (WFLY-7047) host-elytron.xml, different jvm settings, unnecesarry unsecure interface
by Martin Choma (JIRA)
Martin Choma created WFLY-7047:
----------------------------------
Summary: host-elytron.xml, different jvm settings, unnecesarry unsecure interface
Key: WFLY-7047
URL: https://issues.jboss.org/browse/WFLY-7047
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Darran Lofthouse
host-elytron.xml, different jvm settings, unnecesarry unsecure interface
When I compare host-elytron.xml to host.xml,
1) jvm settings use permgen element
2) probably unnecesarry configuration of unsecure profile stays there
Is it worth provide elytron-like host-master/host-slave configuration files for convenience?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7046) domain-elytron.xml doesn't predefine ManagementDomain
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7046?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7046:
----------------------------------------
This one does not sound like a bug, the ManagementDomain lives in the Elytron subsystem within the host.xml and not the domain.xml.
Having said that I probably should have removed all management realms and domains for now and add them back in for phase III so I think my fix for this will just be to remove them all until they are actually needed.
> domain-elytron.xml doesn't predefine ManagementDomain
> -----------------------------------------------------
>
> Key: WFLY-7046
> URL: https://issues.jboss.org/browse/WFLY-7046
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> When I compare domain-elytron.xml to standalone-elytron.xml there is missing ManagementDomain configured in all 4 profiles.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7046) domain-elytron.xml doesn't predefine ManagementDomain
by Martin Choma (JIRA)
Martin Choma created WFLY-7046:
----------------------------------
Summary: domain-elytron.xml doesn't predefine ManagementDomain
Key: WFLY-7046
URL: https://issues.jboss.org/browse/WFLY-7046
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Darran Lofthouse
When I compare domain-elytron.xml to standalone-elytron.xml there is missing ManagementDomain configured in all 4 profiles.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7045) domain-elytron.xml, missing singelton subsystem, different ejb cache type
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7045?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7045:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> domain-elytron.xml, missing singelton subsystem, different ejb cache type
> -------------------------------------------------------------------------
>
> Key: WFLY-7045
> URL: https://issues.jboss.org/browse/WFLY-7045
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> When I compare domain-elytron.xml to domain.xml,
> 1) There is missing org.wildfly.extension.clustering.singleton extension installed.
> 2) There is changed ejb cache configuration
> 1254c1129
> < <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/>
> ---
> > <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7045) domain-elytron.xml, missing singelton subsystem, different ejb cache type
by Martin Choma (JIRA)
Martin Choma created WFLY-7045:
----------------------------------
Summary: domain-elytron.xml, missing singelton subsystem, different ejb cache type
Key: WFLY-7045
URL: https://issues.jboss.org/browse/WFLY-7045
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Darran Lofthouse
When I compare domain-elytron.xml to domain.xml,
1) There is missing org.wildfly.extension.clustering.singleton extension installed.
2) There is changed ejb cache configuration
1254c1129
< <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/>
---
> <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7044) standalone-elytron.xml , unnecessary unsecure interface
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7044?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7044:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> standalone-elytron.xml , unnecessary unsecure interface
> -------------------------------------------------------
>
> Key: WFLY-7044
> URL: https://issues.jboss.org/browse/WFLY-7044
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> When I compare standalone-elytron.xml to standalone.xml, there is additional section
> {noformat}
> </interface>
> <!-- TODO - only show this if the jacorb subsystem is added -->
> <interface name="unsecure">
> <!--
> ~ Used for IIOP sockets in the standard configuration.
> ~ To secure IIOP connections you need to setup SSL
> -->
> <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
> {noformat}
> Is it necessary?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7044) standalone-elytron.xml , unnecessary unsecure interface
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7044?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFLY-7044:
-------------------------------
Summary: standalone-elytron.xml , unnecessary unsecure interface (was: standalone-elytron.xml , unnecesary unsecure interface)
> standalone-elytron.xml , unnecessary unsecure interface
> -------------------------------------------------------
>
> Key: WFLY-7044
> URL: https://issues.jboss.org/browse/WFLY-7044
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
>
> When I compare standalone-elytron.xml to standalone.xml, there is additional section
> {noformat}
> </interface>
> <!-- TODO - only show this if the jacorb subsystem is added -->
> <interface name="unsecure">
> <!--
> ~ Used for IIOP sockets in the standard configuration.
> ~ To secure IIOP connections you need to setup SSL
> -->
> <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
> {noformat}
> Is it necessary?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-7044) standalone-elytron.xml , unnecesary unsecure interface
by Martin Choma (JIRA)
Martin Choma created WFLY-7044:
----------------------------------
Summary: standalone-elytron.xml , unnecesary unsecure interface
Key: WFLY-7044
URL: https://issues.jboss.org/browse/WFLY-7044
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Martin Choma
Assignee: Darran Lofthouse
When I compare standalone-elytron.xml to standalone.xml, there is additional section
{noformat}
</interface>
<!-- TODO - only show this if the jacorb subsystem is added -->
<interface name="unsecure">
<!--
~ Used for IIOP sockets in the standard configuration.
~ To secure IIOP connections you need to setup SSL
-->
<inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
{noformat}
Is it necessary?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months