[JBoss JIRA] (WFCORE-641) The discovery-option "module" attribute should support undefined values
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-641:
---------------------------------------
Summary: The discovery-option "module" attribute should support undefined values
Key: WFCORE-641
URL: https://issues.jboss.org/browse/WFCORE-641
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 1.0.0.CR1
The xsd says the following for the discovery-optionType 'module' attribute:
{code}
<xs:attribute name="module" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>
The module from which the DiscoveryOption implementation should be loaded. If not provided,
the DiscoveryOption implementation must be available from the Host Controller's own module.
</xs:documentation>
</xs:annotation>
</xs:attribute>
{code}
But the MODULE attribute definition does not allow undefined.
But still, DiscoveryOptionAddHandler is coded as if undefined is allowed, but poorly so as it would pass an illegal null into ModuleIdentifier.fromString.
I like the behavior described in the xsd and think the AD and the handlers should be corrected.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4289) Authentication bug on one-way JAX-WS methods
by Jakub Grabowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4289?page=com.atlassian.jira.plugin.... ]
Jakub Grabowski reopened WFLY-4289:
-----------------------------------
According to my previous comment... I tried patching, but still I get not allowed on one-way methods when @RolesAllowed is set on class level.
> Authentication bug on one-way JAX-WS methods
> --------------------------------------------
>
> Key: WFLY-4289
> URL: https://issues.jboss.org/browse/WFLY-4289
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web Services
> Affects Versions: 8.2.0.Final
> Reporter: Jakub Grabowski
> Assignee: Jim Ma
>
> 1. For two-way methods basic authentication and autorization works fine. User is authenticated with LDAP module and gets proper role that autorizes invocation. It works just fine. By two-way method I mean method with input and output message defined in WSDL.
> 2. For one-way methods (return type void) user is not authenticated properly. It results in denial of method invocation.
> 3. When I remove @RolesAllowed declaration I can see that for two-way methods authentication is correct (pricipal is set to logged user), but for one-way it's not - I get "anonymous" as principal.
> 4. When I change one-way method to have input and output messages defined in WSDL and update implementation accordingly it suprisingly starts to work as expected.
> It's quite serious issue, because currently there's no way to have authorized access to oneway webservice methods.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-640) Bad permissions on properties files when using add-user.bat for results in "JBAS015234: No mgmt-groups.properties files found"
by Brandon Gaisford (JIRA)
[ https://issues.jboss.org/browse/WFCORE-640?page=com.atlassian.jira.plugin... ]
Brandon Gaisford commented on WFCORE-640:
-----------------------------------------
Darran,
Regarding the timeliness, understood. I spent a good deal of time over the weekend researching the issue, most notably trying to get my head around Windows file permissions. I feel like I have a good handle on the permissions now and a reasonable Windows 7 test environment. Regarding JDK7, I believe there were updates [1] that may allow AddUser code to check some permissions up front.
In order to limit the scope of the analysis/development I'm going to make some assumptions:
i) Will assume end user installed WildFly directory structure matches that generated by the WildFly build process
ii) Will assume end user file permissions do not prevent user from executing add-user.bat
Will do my best to get you updates (assuming there are some) quickly.
[1] http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6203387
> Bad permissions on properties files when using add-user.bat for results in "JBAS015234: No mgmt-groups.properties files found"
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-640
> URL: https://issues.jboss.org/browse/WFCORE-640
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Environment: Windows 7, 32-bit, jdk1.7.0_45
> Reporter: John Lusk
>
> Just getting started w/Wildfly after a long absence from Java. Fresh download, trying to hit admin console, got instructed to use add-user to add an admin user.
> c:\usr\local\wildfly-8.0.0.Beta1\bin>.\add-user.bat
> What type of user do you wish to add?
> a) Management User (mgmt-users.properties)
> b) Application User (application-users.properties)
> (a): a
> * Error *
> JBAS015234: No mgmt-groups.properties files found.
> Press any key to continue . . .
> c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JBOSS_HOME%
> C:\usr\local\wildfly-8.0.0.Beta1
> c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JAVA_HOME%
> C:\java\jdk1.7.0_45
> c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %M2_HOME%
> C:\usr\local\Maven\3.1.1
> c:\usr\local\wildfly-8.0.0.Beta1\bin>mvn -version
> Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:2
> 2-0400)
> Maven home: C:\usr\local\Maven\3.1.1
> Java version: 1.7.0_45, vendor: Oracle Corporation
> Java home: C:\java\jdk1.7.0_45\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
> c:\usr\local\wildfly-8.0.0.Beta1\bin>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFLY-4289) Authentication bug on one-way JAX-WS methods
by Jakub Grabowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-4289?page=com.atlassian.jira.plugin.... ]
Jakub Grabowski commented on WFLY-4289:
---------------------------------------
[~jim.ma] I've checked resolution by pathching wildfly 8.2 code with the change you mentioned. Unfortunately it doesn't resolve my issue. It works for @PermitAll only, but fails for one-way methods when there's RolesAllowed on class level. Have you check this scenario?
> Authentication bug on one-way JAX-WS methods
> --------------------------------------------
>
> Key: WFLY-4289
> URL: https://issues.jboss.org/browse/WFLY-4289
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web Services
> Affects Versions: 8.2.0.Final
> Reporter: Jakub Grabowski
> Assignee: Jim Ma
>
> 1. For two-way methods basic authentication and autorization works fine. User is authenticated with LDAP module and gets proper role that autorizes invocation. It works just fine. By two-way method I mean method with input and output message defined in WSDL.
> 2. For one-way methods (return type void) user is not authenticated properly. It results in denial of method invocation.
> 3. When I remove @RolesAllowed declaration I can see that for two-way methods authentication is correct (pricipal is set to logged user), but for one-way it's not - I get "anonymous" as principal.
> 4. When I change one-way method to have input and output messages defined in WSDL and update implementation accordingly it suprisingly starts to work as expected.
> It's quite serious issue, because currently there's no way to have authorized access to oneway webservice methods.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (JBJCA-1261) Rework pool policies
by Jesper Pedersen (JIRA)
Jesper Pedersen created JBJCA-1261:
--------------------------------------
Summary: Rework pool policies
Key: JBJCA-1261
URL: https://issues.jboss.org/browse/JBJCA-1261
Project: IronJacamar
Issue Type: Task
Components: Core
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.2.4.Final
Let the pool policy (FIFO/FILO) be defined by its decrementer policy
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (WFCORE-631) Wildcard operation inside composite is missing address node
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-631?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-631:
-----------------------------------------
Damn I'm good! ;)
Highly likely this was fixed as part of the WFCORE-282 work (see PR linked there), which took so long because I kept stumbling upon and sorting problems with the response structures, particularly the combination of wildcard reads and composites.
> Wildcard operation inside composite is missing address node
> -----------------------------------------------------------
>
> Key: WFCORE-631
> URL: https://issues.jboss.org/browse/WFCORE-631
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: Brian Stansberry
> Priority: Blocker
>
> The result of a composite operation which contains a {{read-resource}} operation with wildcards is missing the {{address}} node.
> {code:title=WildFly 9|borderStyle=solid}
> [domain@localhost:9990 /] batch
> [domain@localhost:9990 / #] /server-group=*/deployment=*:read-resource
> [domain@localhost:9990 / #] run-batch --verbose
> {
> "outcome" => "success",
> "result" => {"step-1" => {
> "outcome" => "success",
> "result" => [{
> "address" => undefined,
> "outcome" => undefined,
> "result" => {
> "enabled" => false,
> "name" => "jboss-as-login.war",
> "runtime-name" => "jboss-as-login.war"
> }
> }]
> }},
> "server-groups" => undefined
> }
> {code}
> {code:title=WildFly 8.2.0|borderStyle=solid}
> [domain@localhost:9990 /] batch
> [domain@localhost:9990 / #] /server-group=*/deployment=*:read-resource
> [domain@localhost:9990 / #] run-batch --verbose
> {
> "outcome" => "success",
> "result" => {"step-1" => {
> "outcome" => "success",
> "result" => [{
> "address" => [
> ("server-group" => "main-server-group"),
> ("deployment" => "test-application.war")
> ],
> "outcome" => undefined,
> "result" => {
> "enabled" => false,
> "name" => "test-application.war",
> "runtime-name" => "test-application.war"
> }
> }]
> }},
> "server-groups" => undefined
> }
> {code}
> Executing the {{read-resource}} op itself yields the same result for WildFly 8.2.0.Final and 9
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months