[
https://issues.apache.org/jira/browse/KARAF-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907124#action_12907124
]
Ioannis Canellos commented on KARAF-188:
----------------------------------------
It could work like the config command:
ka...@root> jaas:manage <jaas config name>
ka...@root> jaas:useradd <username> <password> (with optional arguments that
could control encryption?)
ka...@root> jaas:passwd <username> <password> (with optional arguments that
could control encryption?)
ka...@root> jaas:roleadd <username> <role>
ka...@root> jaas:roledel <username> <role>
ka...@root> jaas:list
ka...@root> jaas:cancel
ka...@root> jaas:update
This way the user management would be independent to the underlying backing
engine.
For this to happen we will either need that logic implemented inside the login
module, or we will need to specify for each jaas config a the useradmin service
implementation specific to the backing engine (not 100% sure if this covers all
the needs).
> Provide commands to manage users, passwords and roles
> -----------------------------------------------------
>
> Key: KARAF-188
> URL: https://issues.apache.org/jira/browse/KARAF-188
> Project: Karaf
> Issue Type: New Feature
> Reporter: Guillaume Nodet
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
