Skip to content

Conversation

pedro-hos
Copy link

Issue: #711
Jira: WFLY-20384

@github-actions github-actions bot added the invalid-categories The categories field in the proposal metadata is not valid label Apr 4, 2025
@pedro-hos pedro-hos force-pushed the WFLY-20384 branch 2 times, most recently from 3294b3e to 769a4f3 Compare April 4, 2025 14:09
@github-actions github-actions bot added stability-level/community "Community" stability level and removed invalid-categories The categories field in the proposal metadata is not valid labels Apr 4, 2025
=== Changed requirements
Update the schema n order to add the new `properties-role-mapper` configuration.

=== Non-Requirements
Copy link

@OndrejKotek OndrejKotek Apr 24, 2025

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.

Copy link
Contributor

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.

Copy link

@OndrejKotek OndrejKotek Apr 24, 2025

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?

Copy link
Author

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

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?

Copy link
Author

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.

Copy link

@OndrejKotek OndrejKotek May 12, 2025

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.

@github-actions github-actions bot added stability-level/community "Community" stability level and removed stability-level/community "Community" stability level labels May 26, 2025
@pedro-hos pedro-hos requested review from darranl and OndrejKotek May 26, 2025 20:39
…dule in the mapped role mapper

ading feature team
@github-actions github-actions bot added stability-level/community "Community" stability level and removed stability-level/community "Community" stability level labels Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stability-level/community "Community" stability level
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants