This will add the events tab if enabled and authorized to:

• ClientScopes (Admin Events)
• Clients (User- and Admin Events)
• Groups (Admin Events + Membership and Childgroup assignments events)
• Identity-Providers (Admin Events)
• Organizations (Admin Events + Membership events)
• RealmRole (Admin Events)
• User (User- and Admin Events)

Hi @antikalk, many thanks for this and your previous contribution.

We had to change this PR to a draft as we realized that some improvements were necessary after merging your previous PR: #34561. You can view these changes here: #34735 .

Now that these improvements are in place, we can proceed with this PR. However, I'd appreciate it if you could review the current implementation of the event tabs for Clients and Users as introduced in #34735 and make any relevant changes to this PR.

Let's keep this PR as a draft until it's ready for review. Thanks!

@agagancarczyk I have updated the branch to include the changes. During development I noticed two changes:

• As the activeFilters will not be initialized with the User-/Client param value anymore, the chip indicating the filter is not displayed initially. When I add an additional filter, or simply open and submit the filter menu, the chip will be displayed though. IMO it would make sense to hide the chip for a value that has been a component param all the time.
• When there is no events being found initially the toolbarItem is hidden. I guess this is fine as no events will be available to filter for anyways.

@agagancarczyk I have updated the branch to include the changes. During development I noticed two changes:

• As the activeFilters will not be initialized with the User-/Client param value anymore, the chip indicating the filter is not displayed initially. When I add an additional filter, or simply open and submit the filter menu, the chip will be displayed though. IMO it would make sense to hide the chip for a value that has been a component param all the time.
• When there is no events being found initially the toolbarItem is hidden. I guess this is fine as no events will be available to filter for anyways.

Thanks @antikalk 1. Yes, we should hide the chip. 2. Yes, this behavior makes sense

@agagancarczyk I provided the change to the filter chips with this PR.

@antikalk Please fix conflicts.

@ssilvert done

I was trying this out. Looks really nice.

I did notice one flaw in the empty state of all events. It's a general problem, but this PR makes it more relevant. See screen shot of admin events for a realm role:

Notice that it says, There are no admin events in this realm., which doesn't make a lot of sense for realm events. But also, there is no way to refresh this screen.

I think the best solution is to just replace the message There are no admin events in this realm. with a refresh button/link.

@antikalk Sorry. Please fix conflicts again.

Will you be addressing the empty state issue I raised? If not, we can do it in another issue/PR.

@ssilvert I fixed the conflicts. In my opinion it would make sense to address the empty state issue in a different issue/pr.

Any chance of getting this into 26.1? Should we include the feature in the release notes?

Thanks for the contribution @antikalk.

I created the cleanup issue: #36413