I had solved this by deploying a blueprint bundle on the lines of:
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;>
(I had my own custom JAAS class, but for this snippet I put the
PropertiesLoginModule instead.
Hi Paul
It's not a bug, that's an expected behavior: the JAAS configuration
created by the commands is stored "in memory".
If you want to persist, you have to use blueprint jaas namespace (in
the deploy folder for instance).
I plan to remove this "requirement" for Karaf 4.5.x using another
