-
Notifications
You must be signed in to change notification settings - Fork 81
[WFLY-20384] - Restore the original behaviour of RoleMapping login module in the mapped role mapper #712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
3294b3e
to
769a4f3
Compare
=== Changed requirements | ||
Update the schema n order to add the new `properties-role-mapper` configuration. | ||
|
||
=== Non-Requirements |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUIC, the original login module is able to load also property files from deployments: https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/7.4/html-single/login_module_reference/index#rolemapping_login_module I assume such functionality is not planned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No managed components should be loading from deployed content.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, the original module provides replaceRole
option. Also out of the scope?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@OndrejKotek I think that we can add this option as well, there are other mappers which already have this implemented. What do you think @darranl ?
=== Future Work | ||
N/A | ||
|
||
== Backwards Compatibility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to use a file for the original login module directly without changes in the new mapper?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am sorry, I didn't got your question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the Backward Compatibility section should discuss how migrate from the original login module to the new Elytron based/integrated solution. The configuration is completely different and there is not much to be compatible (replaceRole
option?), the data/properties file used by the configuration should be ideally usable as is without modifications. My question/suggestion is to write here an assurance that the properties file can be used without any changes when migrating from the original login module to Elytron.
…dule in the mapped role mapper ading feature team
Issue: #711
Jira: WFLY-20384