[JBoss JIRA] (WFLY-7101) Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-7101?page=com.atlassian.jira.plugin.... ]
jaikiran pai moved WFCORE-1782 to WFLY-7101:
--------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-7101 (was: WFCORE-1782)
Component/s: EJB
(was: Server)
Affects Version/s: 10.1.0.Final
(was: 2.2.0.Final)
Fix Version/s: (was: 2.2.1.Final)
> Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct
> --------------------------------------------------------------
>
> Key: WFLY-7101
> URL: https://issues.jboss.org/browse/WFLY-7101
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.1.0.Final
> Environment: Wildfly 10.1.0 running under Windows 10 with Java 1.8.0_91
> Reporter: Dietrich Schmidt
> Assignee: Jason Greene
> Attachments: Verklemmung.zip
>
>
> Wildfly 8.2.0 and 10.0.0 work fine with a Singleton Bean, which has a @Postconstruct method and in this method several threads are created with the ManagedExecutorService. These threads call a method in another Singleton EJB, which has been injected.
> This call is blocked in Wildfly 10.1.0 until the Prostconstruct thread has ended.
> I assume that the behaviour of Wildfly 8.2.0 + 10.0.0 is correct and the behaviour of Wildfly 10.1.0 is a bug.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1742) Allow registering a custom handler for management interface
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1742?page=com.atlassian.jira.plugi... ]
Sebastian Łaskawiec commented on WFCORE-1742:
---------------------------------------------
Infinispan also has a custom management console for the record.
I think a short limited mapping api would be ok (at least for us). Something like map this long URI to this short URI. It gets slightly more interesting when we need to change HTTP methods - e.g. showing runtime resources requires sending HTTP PUT (not GET)...
> Allow registering a custom handler for management interface
> -----------------------------------------------------------
>
> Key: WFCORE-1742
> URL: https://issues.jboss.org/browse/WFCORE-1742
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Sebastian Łaskawiec
>
> When building [HealthCheck API for Infisnispan|https://github.com/infinispan/infinispan/pull/4499] we noticed there is no way to register a custom endpoint on Management REST interface. Without it, calling the API requires using HTTP POST method (since it includes runtime parameters) and the URL is very long (and not intuitive for our users):
> {noformat}
> curl --digest -L -D - "http://localhost:9990/management/subsystem/datagrid-infinispan/cache-cont..." --header "Content-Type: application/json" -u ispnadmin:ispnadmin
> HTTP/1.1 401 Unauthorized
> Connection: keep-alive
> WWW-Authenticate: Digest realm="ManagementRealm",domain="/management",nonce="AuZzFxz7uC4NMTQ3MDgyNTU1NTQ3OCfIJBHXVpPHPBdzGUy7Qts=",opaque="00000000000000000000000000000000",algorithm=MD5,qop="auth"
> Content-Length: 77
> Content-Type: text/html
> Date: Wed, 10 Aug 2016 10:39:15 GMT
> HTTP/1.1 200 OK
> Connection: keep-alive
> Authentication-Info: nextnonce="AuZzFxz7uC4NMTQ3MDgyNTU1NTQ3OCfIJBHXVpPHPBdzGUy7Qts=",qop="auth",rspauth="b518c3170e627bd732055c382ce5d970",cnonce="NGViOWM0NDY5OGJmNjY0MjcyOWE4NDkyZDU3YzNhYjY=",nc=00000001
> Content-Type: application/json; charset=utf-8
> Content-Length: 1927
> Date: Wed, 10 Aug 2016 10:39:15 GMT
> {
> "cache-health" : "GREEN",
> "cluster-health" : ["test"],
> "cluster-name" : "clustered",
> "free-memory" : 96778,
> "log-tail" : [
> "2016-08-10 11:54:14,706 INFO [org.infinispan.server.endpoint] (MSC service thread 1-5) DGENDPT10001: HotRodServer listening on 127.0.0.1:11222",
> "2016-08-10 11:54:14,706 INFO [org.infinispan.server.endpoint] (MSC service thread 1-1) DGENDPT10001: MemcachedServer listening on 127.0.0.1:11211",
> "2016-08-10 11:54:14,785 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-6) DGISPN0001: Started ___protobuf_metadata cache from clustered container",
> "2016-08-10 11:54:14,800 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-6) DGISPN0001: Started ___script_cache cache from clustered container",
> "2016-08-10 11:54:15,159 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-5) DGISPN0001: Started ___hotRodTopologyCache cache from clustered container",
> "2016-08-10 11:54:15,210 INFO [org.infinispan.rest.NettyRestServer] (MSC service thread 1-6) ISPN012003: REST server starting, listening on 127.0.0.1:8080",
> "2016-08-10 11:54:15,210 INFO [org.infinispan.server.endpoint] (MSC service thread 1-6) DGENDPT10002: REST mapped to /rest",
> "2016-08-10 11:54:15,306 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management",
> "2016-08-10 11:54:15,307 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990",
> "2016-08-10 11:54:15,307 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: Infinispan Server 9.0.0-SNAPSHOT (WildFly Core 2.2.0.CR9) started in 8681ms - Started 196 of 237 services (121 services are lazy, passive or on-demand)"
> ],
> "number-of-cpus" : 8,
> "number-of-nodes" : 1,
> "total-memory" : 235520
> }%
> {noformat}
> It would be very convenient to allow exposing such endpoints with optional authorization and using custom URLs (e.g. something like http://localhost:9990/health).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7096) Security domain casche dosn't respect infinispan settings
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7096?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7096:
----------------------------------------
The Infinispan cache setting is something left over from initial development in 2011 - to properly support Infinispan based caching both the cache container and the name of the cache would need to be configurable within the security subystem.
> Security domain casche dosn't respect infinispan settings
> ---------------------------------------------------------
>
> Key: WFLY-7096
> URL: https://issues.jboss.org/browse/WFLY-7096
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 10.0.0.Final, 10.1.0.Final
> Environment: Tested on Windows 7
> Reporter: Marcin Fatyga
> Assignee: Darran Lofthouse
> Attachments: patch.txt, standalone.xml, test_webapp.zip
>
>
> In securitydomain we can set "casche-type" to infinispan. Auntentication request ara now stored in infinispan casch, but any settings of this casche (configured in infinispan subsystem) are not applied. Casche is always stored in memory and never expiries.
> This is serious security issue because after first authentication request credentials, will never be verified again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7096) Security domain casche dosn't respect infinispan settings
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7096?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7096:
-----------------------------------
Issue Type: Feature Request (was: Bug)
> Security domain casche dosn't respect infinispan settings
> ---------------------------------------------------------
>
> Key: WFLY-7096
> URL: https://issues.jboss.org/browse/WFLY-7096
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 10.0.0.Final, 10.1.0.Final
> Environment: Tested on Windows 7
> Reporter: Marcin Fatyga
> Assignee: Darran Lofthouse
> Attachments: patch.txt, standalone.xml, test_webapp.zip
>
>
> In securitydomain we can set "casche-type" to infinispan. Auntentication request ara now stored in infinispan casch, but any settings of this casche (configured in infinispan subsystem) are not applied. Casche is always stored in memory and never expiries.
> This is serious security issue because after first authentication request credentials, will never be verified again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7096) Security domain casche dosn't respect infinispan settings
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7096?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7096:
-----------------------------------
Security Sensitive Issue: (was: This issue is security relevant)
> Security domain casche dosn't respect infinispan settings
> ---------------------------------------------------------
>
> Key: WFLY-7096
> URL: https://issues.jboss.org/browse/WFLY-7096
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.0.Final, 10.1.0.Final
> Environment: Tested on Windows 7
> Reporter: Marcin Fatyga
> Assignee: Darran Lofthouse
> Attachments: patch.txt, standalone.xml, test_webapp.zip
>
>
> In securitydomain we can set "casche-type" to infinispan. Auntentication request ara now stored in infinispan casch, but any settings of this casche (configured in infinispan subsystem) are not applied. Casche is always stored in memory and never expiries.
> This is serious security issue because after first authentication request credentials, will never be verified again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7096) Security domain casche dosn't respect infinispan settings
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7096?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7096:
-----------------------------------
Security: (was: Security Issue)
> Security domain casche dosn't respect infinispan settings
> ---------------------------------------------------------
>
> Key: WFLY-7096
> URL: https://issues.jboss.org/browse/WFLY-7096
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 10.0.0.Final, 10.1.0.Final
> Environment: Tested on Windows 7
> Reporter: Marcin Fatyga
> Assignee: Darran Lofthouse
> Attachments: patch.txt, standalone.xml, test_webapp.zip
>
>
> In securitydomain we can set "casche-type" to infinispan. Auntentication request ara now stored in infinispan casch, but any settings of this casche (configured in infinispan subsystem) are not applied. Casche is always stored in memory and never expiries.
> This is serious security issue because after first authentication request credentials, will never be verified again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-7082) Adding simple-permission-mapper with some permission throws NPE
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7082?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7082:
----------------------------------
Problem is in missing *target-name* attribute:
{code:xml}
<permission class-name="org.wildfly.security.auth.permission.ChangeRoleMapperPermission" target-name="test" />
{code}
Without it ChangeRoleMapperPermission.getName() returns null, which is not acceptable by *ByNamePermissionCollection*.
I will improve error handling.
> Adding simple-permission-mapper with some permission throws NPE
> ---------------------------------------------------------------
>
> Key: WFLY-7082
> URL: https://issues.jboss.org/browse/WFLY-7082
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
>
> Adding simple-permission-mapper with ChangeRoleMapperPermission or RunAsPrincipalPermission throws NPE. In case when LoginPermission is used then it works correctly.
> {code}
> /subsystem=elytron/simple-permission-mapper=SomeMapper:add(permission-mappings=[{roles=[All],permissions=[{class-name="org.wildfly.security.auth.permission.ChangeRoleMapperPermission"}]}])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.permission-mapper.SomeMapper" => "org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.SomeMapper: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.permission-mapper.SomeMapper"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {code}
> NPE occurs in server log:
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.permission-mapper.SomeMapper: org.jboss.msc.service.StartException in service org.wildfly.security.permission-mapper.SomeMapper: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.security.permission.ByNamePermissionCollection.doAdd(ByNamePermissionCollection.java:59)
> at org.wildfly.security.permission.AbstractPermissionCollection.add(AbstractPermissionCollection.java:83)
> at java.security.Permissions.add(Permissions.java:133)
> at org.wildfly.extension.elytron.PermissionMapperDefinitions.createSimplePermissionMapper(PermissionMapperDefinitions.java:214)
> at org.wildfly.extension.elytron.PermissionMapperDefinitions.access$000(PermissionMapperDefinitions.java:67)
> at org.wildfly.extension.elytron.PermissionMapperDefinitions$2.lambda$getValueSupplier$0(PermissionMapperDefinitions.java:188)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months