-
1. Re: Dynamically add security domain with war deployment.
mchoma Oct 19, 2017 11:43 AM (in response to fabi.yo.4)Which wildfly version are we talking here about?
In recent versions you can add security domain only via standalone.xml. Do you know about possibility to configure wildfly with CLI commands? In the end standalone.xml is changed. Is it option for you? You can call that automatically from script.
-
2. Re: Dynamically add security domain with war deployment.
fabi.yo.4 Oct 20, 2017 4:43 AM (in response to mchoma)WildFly 10+.
Yes I am aware of CLI. The purpose is to add everything in my war. I can add a datasource which in the end is simply the same datasource as the standalone, only in a separate xml file which is present in the deployed war (jboss-ds.xml).
The CLI looks only useful to me when managing thousands of servers and you don't want to go edit each standalone.xml separetely. I always edit directly the standalone.xml.
-
3. Re: Dynamically add security domain with war deployment.
mchoma Oct 20, 2017 5:29 AM (in response to fabi.yo.4)There is nothing like that - separate xml file to configure security domains.
With CLI you can automate things. For example 1. configure server with CLI 2. deploy war. For example with wildfly maven plugin.
PicketBox security domains are just JAAS Login Modules. So in theory you could use java process wide jaas.conf, e.g. java -Djava.security.auth.login.config=jaas.conf. But I really wouldn't go this way
-
4. Re: Dynamically add security domain with war deployment.
fabi.yo.4 Oct 20, 2017 5:39 AM (in response to mchoma)Ok tnx for the clarification!