Ciprian,
Thank you. I found the following supporting documentation and was able to
create a new realms.
https://karaf.apache.org/manual/latest/#_available_realm_and_login_modules
Paul Spencer
On 2024/01/31 15:15:32 Ciprian Ciubotariu wrote:
> I had solved this by deploying a blueprint
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
Karaf 4.4.5
JVM OpenJDK 64-Bit Server VM version 11.0.2+9
A realm created via jaas:realm-add is not listed after karaf restart. This may
be related to KARAF-7602.
- Create the realm using the following commands:
jaas:realm-add myrealm
