[JBoss JIRA] (DROOLS-1193) MemoryUtil's static constructor call to ManagementFactory.getMemoryPoolMXBeans() fails on Google App Engine
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1193?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1193:
------------------------------------------
After discussion we saw 3 alternative:
* A) Disable the feature (such as jitting constraints) if BeanManager isn't available on JDK 7 or lower - Accepted
* B) Pessmistically guess the permGenspace value - Rejected because it's unreliabe/unstable. It's also impossible to ask later on how much is left.
* C) Allow enabling/disabling each feature individually through configuration - Rejected because it's inferior to A): too much painfully hoops for a user to jump through.
How do we detect GAE (and Android etc) best? Still under debate:
http://stackoverflow.com/questions/37463518/how-to-detect-google-app-engi...
> MemoryUtil's static constructor call to ManagementFactory.getMemoryPoolMXBeans() fails on Google App Engine
> -----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1193
> URL: https://issues.jboss.org/browse/DROOLS-1193
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> {code}
> [INFO] java.lang.NoClassDefFoundError: java.lang.management.ManagementFactory is a restricted class. Please see the Google App Engine developer's guide for more details.
> [INFO] at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:52)
> [INFO] at org.drools.core.util.MemoryUtil.<clinit>(MemoryUtil.java:33)
> [INFO] at java.lang.Class.forName0(Native Method)
> [INFO] at java.lang.Class.forName(Class.java:195)
> [INFO] at com.google.appengine.tools.development.agent.runtime.RuntimeHelper.checkRestricted(RuntimeHelper.java:70)
> [INFO] at com.google.appengine.tools.development.agent.runtime.Runtime.checkRestricted(Runtime.java:65)
> [INFO] at org.drools.core.RuleBaseConfiguration.setPermGenThreshold(RuleBaseConfiguration.java:583)
> [INFO] at org.drools.core.RuleBaseConfiguration.init(RuleBaseConfiguration.java:451)
> [INFO] at org.drools.core.RuleBaseConfiguration.init(RuleBaseConfiguration.java:429)
> [INFO] at org.drools.core.RuleBaseConfiguration.<init>(RuleBaseConfiguration.java:278)
> [INFO] at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieBaseConfiguration(KieServicesImpl.java:185)
> {code}
> the problem is in this code:
> {code}
> static {
> if (!hasPermGen() || ClassUtils.isAndroid()) { // hasPermGen is true because GAE doesn't support java 8 yet
> permGenStats = new DummyMemoryStats();
> } else {
> MemoryPoolMXBean permGenBean = null;
> for (MemoryPoolMXBean mx : ManagementFactory.getMemoryPoolMXBeans()) { // <=== EXCEPTION
> if (mx.getName() != null && mx.getName().contains("Perm")) {
> permGenBean = mx;
> break;
> }
> }
> permGenStats = new MBeanMemoryStats(permGenBean);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-377) Add a SecurityFactory implementation to return a GSSCredential
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-377?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on ELY-377:
--------------------------------------
Either this issue or ELY-454 will be rejected as a duplicate as they both propose solutions for the same problem - will know shortly as I am writing the Kerberos integration for HTTP now.
> Add a SecurityFactory implementation to return a GSSCredential
> --------------------------------------------------------------
>
> Key: ELY-377
> URL: https://issues.jboss.org/browse/ELY-377
> Project: WildFly Elytron
> Issue Type: Task
> Components: Utils
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta6
>
>
> This task is for a simple implementation that uses a JAAS call and the GSSAPI APIs to authenticate and obtain the GSSCredential.
> For completeness this utility should probably cover both the client side and server side use cases.
> Delegation however may call for a slightly different implement for the client side when running in a server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-508) A USERNAME HTTP authentication mechanism.
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-508?page=com.atlassian.jira.plugin.sy... ]
Farah Juma reassigned ELY-508:
------------------------------
Assignee: Farah Juma
> A USERNAME HTTP authentication mechanism.
> -----------------------------------------
>
> Key: ELY-508
> URL: https://issues.jboss.org/browse/ELY-508
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Farah Juma
> Fix For: 2.0.0.Alpha1
>
>
> This is closely related to FORM authentication but to cover the case where we want to prompt for just a username first and once we know that the subsequent challenge can be customised.
> The customisation may be by separate authentication mechanisms then able to offer their own specific FORM variant and perform their own validation.
> As an example we may prompt one user for a password whilst prompt a different user for a password and a OTP, we could even use this to decide if we authenticate against a local realm with a credential or redirect via something like KeyCloak.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ELY-509) Multi Step HTTP Authentication
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-509?page=com.atlassian.jira.plugin.sy... ]
Farah Juma reassigned ELY-509:
------------------------------
Assignee: Farah Juma (was: Darran Lofthouse)
> Multi Step HTTP Authentication
> ------------------------------
>
> Key: ELY-509
> URL: https://issues.jboss.org/browse/ELY-509
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Farah Juma
> Fix For: 1.1.0.Beta7
>
>
> This is a variation of FORM authentication and closely related to ELY-508.
> The scenario would be prompt for a username, then prompt for a password and if the password is valid and the account supports OTP prompt for the OTP.
> The mechanism may also be responsible for sending the OTP but that is probably a side topic.
> I have raised this in terms of being a HTTP mechanism but the main point we need to ensure is covered is the requirements about identifying what checks are required for a specific user and tracking they are all complete.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months