I'm looking to configure some settings present in the version of Infinispan shipped with Keycloak's Wildfly from the following Infinispan provided xsd:
infinispan-config-8.2.xsd
The settings I'm looking for ('global-state' element) aren't present in the jboss-as-infinispan_4_0.xsd schema, though.
How do I leverage configuration features the version shipped with Wildfly supports?
I apologize if this is obvious (I'm new to Wildfly). I've spent a fair amount of time researching and am starting to think it cannot be done without write a custom submodule. Any pointers would be appreciated.
Related
All over the internet CVE-2022-34169, this vulnerability is popping up now.
The older Keycloak (JBoss server) and many other applications are heavily using xalan jar and it is dependent on many other libraries.
Does anyone know how to fix or remediate this vulnerability?
Here is some example of how Keycloak and other library is dependent on this.
Keycloak/modules/system/layers/base/com/sun/jsf-impl/main/module.xml
Keycloak/modules/system/layers/base/org/apache/santuario/xmlsec/main/module.xml
Keycloak/modules/system/layers/base/org/apache/xalan/main/xalan-2.7.2.jar
Keycloak/modules/system/layers/base/org/jboss/as/jdr/main/module.xml
Keycloak/modules/system/layers/base/org/jboss/as/standalone/main/module.xml
Keycloak/docs/licenses/full-feature-pack-licenses.html
Keycloak/docs/licenses/full-feature-pack-licenses.xml
Keycloak/modules/system/layers/base/org/apache/ws/security/main/module.xml
Keycloak/modules/system/layers/base/org/apache/xalan/main/module.xml
Keycloak/modules/system/layers/base/javax/servlet/jstl/api/main/module.xml
Keycloak/modules/system/layers/base/org/jboss/as/host-controller/main/module.xml
Keycloak/modules/system/layers/base/org/jboss/as/webservices/server/integration/main/module.xml
Keycloak/modules/system/layers/base/org/jboss/as/cli/main/module.xml
Keycloak/modules/system/layers/base/org/jboss/as/appclient/main/module.xml
Keycloak/modules/system/layers/base/org/wildfly/bootable-jar/main/module.xml
Keycloak/modules/system/layers/base/org/jboss/as/server/main/module.xml
Pardon if I can't give more pointers, but I'm really a noob at wildfly. I'm using version 9.0.2.
I have deployed jbpm-console, drools, and dashboard - no problems here. I restart wildfly using the jboss CLI, and when I login again, the repositories won't appear in the web interface or on disk (atleast nothing that grepping or find will show).
I'm using the H2 database. I'm not even sure where to look, does anyone have any idea?
Thanks in advance!
After enough reading through the docs, it would seem that it's necessary to configure jBPM to persist. From the docs:
"By default, the engine does not save runtime data persistently. This means you can use the engine completely without persistence (so not even requiring an in memory database) if necessary, for example for performance reasons, or when you would like to manage persistence yourself. It is, however, possible to configure the engine to do use persistence by configuring it to do so. This usually requires adding the necessary dependencies, configuring a datasource and creating the engine with persistence configured."
https://docs.jboss.org/jbpm/v5.3/userguide/ch.core-persistence.html
There are couple of datasource configuration files for XA and NON-XA datasource in JBOSS v4.2.3 for the various need of the deployed applications in the jboss environment. Also the DB passwords are encrypted using the JBOSS provided techniques (some datasources are created using JaasSecurityDomain and some use SecureIdentityLoginModule) .
How these datasource configurations and these encryption methodologies are going to behave in jboss v5 and jbossv7 ?
Is there any JBOSS tool/utility to convert the datasource to the corresponding new JBOSS version and also take care of the encryption password part ?
What is the best way to migrate these datasources created with the password encrypted.
Any help in this topic is highly appreciated .
Regards,
Jiten
Take a look at Windup project http://windup.jboss.org/
that is aiming to provide as automated upgrade as possible.
As mentioned in the article https://community.jboss.org/wiki/DataSourceConfigurationInAS7 JBoss 7 provides 2 main ways to configure a data source.
What is the BEST practice of configuring a data source in JBoss 7 AS ? Is it
As a module?
As a deployment?
(The same question has been asked in the thread https://community.jboss.org/thread/198023, but no one has provided an acceptable answer yet.)
The guide JBoss AS7 DS configuration says the recommended way is to configure the datasource by deployment
But according to discussion on the link Jboss 7 DS configuration JBoss Community Discussion on page 54 of the guide it mentions that the recommended way to deploy JDBC driver is to use modular approach
But I personally say that the better(not the best) approach to configure JDBC driver would be to use modules because of 3 reasons
JDBC driver will generally not change.
Re-usability : You can use the same module across various applications and not deploy the jar along with each application, this prevents duplicacy
Space Effective : Using the module approach lets you reduce the size of your EAR/WAR as you do not need to supply the jar with the package
Hence I would argue that the better of the two approaches is via modules
#Mukul Goel
It's not necessary to include it the EAR of your application it's sufficient to put the .jar inside the deployments folder so:
no need to embed in ear
no need to create a module
Jist deploy in deployments folder or via admin console
we are migrating one application from JBoss AS 6 to 7.
This new instance is useing the standalone-ha profile. On the previous version, we used a custom Infinispan loader which stored the cache entries into our custom database.
Now, on JBoss 7.1, when trying to change this configuration using the visual administration console, it don't work. The value that we type on the tab "Store Class Impl" on "Replicated caches" is not being stored on the profile configuration as it should be. So, here is my question: is it possible to change this configuration using xml? How can I configure this custom loader for our replicated caches? Does anyone here ever experience this kind of dificulty?
Unfortunately I can't provide you any valuable information about JBoss admin console.
Anyway, I would suggest you to set up cache stores/loaders for your Infinispan caches declaratively (using configuration xml file) or programmatically (using fluent API builder just in code).
Here you can find more details about stores/loaders and some example configurations: https://docs.jboss.org/author/display/ISPN/Cache+Loaders+and+Stores
And also take into account that in the recent Infinispan version (5.2) there is no possibility to change cache configuration "on fly". You need to restart your service with new configuration in case of any wanted change.
(What do you exactly mean by custom Infinispan loader?)