[ https://issues.jboss.org/browse/WFLY-6642?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-6642: --------------------------------- Description: I propose that the transport config parameters configured in ior settings, which later are present in the description of all corba object IORs created in the server, are created automatically. I don't like the idea of manual configuration as it provides invalid description of actual transport parameters in most circumstances. We are providing either standard socket transport or (if configured) SSL transport. Currently user is responsible for providing transport description. So if for example user configures SSL transport but doesn't change transport config then transport description in ior settings is invalid. What is more transport config is currently used to configure required SSL connection - that is if user wants to configure SSL connection he has to specify at least one SSL related transport field as required. This is imo inelegant and not much user friendly. I propose the following change: transport config is created automatically. If user configures SSL then all transport fields provided by SSL (f.e. confidentiality) will be set as supported. To configure required ssl connections server-requires-ssl field in security tag is introduced. If this field is set to true, then all SSL transport fields will be set as required. (was: I propose that the transport config parameters configured in ior settings, which later are present in the description of all corba object IORs created in the server, are created automatically. I don't like the idea of manual configuration as it provides invalid description of actual transport parameters in most circumstances. We are providing either standard socket transport or (if configured) SSL transport. Currently user is responsible for providing transport description. So if for example user configures SSL transport but doesn't change transport config then transport description in ior settings is invalid. What is more transport config is currently used to configure required SSL connection - that is if user wants to configure SSL connection he has to specify at least one SSL related transport field as required. This is imo inelegant and not much user friendly. I propose the following change: transport config is created automatically. If user configures SSL then all transport fields provided by SSL (f.e. confidentiality) will be set as supported. I also introduction of boolean field server-requires-ssl in security tag. If this field is set to true, then all SSL transport fields will be set as required. ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)