Skip to content
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

LMSA-9652 - added event authorization event publisher and removed the… #30

Merged
merged 6 commits into from
Feb 10, 2025

Conversation

dsobiera
Copy link
Contributor

@dsobiera dsobiera commented Feb 7, 2025

… old way of doing authorization event registration

@Component
@Slf4j
public class LmsAuthorizationEventPublisher implements AuthorizationEventPublisher {
private ApplicationEventPublisher applicationEventPublisher;
Copy link
Contributor Author

@dsobiera dsobiera Feb 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we put this publisher in a common place (vs in the tool here) like the old stuff was? And by publisher I mean this whole class/file. The issue doing that is that anything using that common place will be publishing authorization events. And, perhaps, that's okay?


import java.util.function.Supplier;

@Profile("it12")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would we want to use this profile to turn authorization event publishing on? If so, we'd have to change the runtime profiles for our apps that use this (to help community runs by leaving this off). Otherwise, we'd remove this profile and always have authorization event publishing on

@dsobiera dsobiera merged commit a576bc9 into main Feb 10, 2025
4 checks passed
@dsobiera dsobiera deleted the LMSA-9652_fix_authorization_logging branch February 10, 2025 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants