Log which attributes (not values) are released per IdP

New Feature Request

Summary

Problem: When communicating with SPs/RPs, the federation operator now cannot tell which attributes are available from the connected IdP's.

Value: This gives the federation operator insight in what attributes are available from which IdP, so attributes can be predicably released to SPs/RPs, according to the attribute release policy. This assumes attributes are filled with valid values, addressing that is a separate problem.

Proposed Solution

• Action: For each authentication, log what IdP was used and which attributes (not values) were released by the IdP.
  Possibly aggregate the data in EB itself.

• Design: [Link to Figma/Screenshots]

• Impact: Does this affect existing APIs or UI components?

Developer Checklist

To be completed by the developer during implementation.

• Add required changes and feature flags config files
• Create and document database changes and migrations
• Create and document API changes and migrations
• check for backwards compatibility
• Updated CHANGELOG and other documentation where needed

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup

1. Point to [URL/Branch]
2. Use account with [Role/Permissions]

Test Checklist

• Happy Path: Feature works as intended under normal conditions.
• Edge Case: [Describe specific test item]
• Validation: [Describe specific test item]
• UI/UX: Verified layout across screen sizes.

Extra Information

Add any other context, related issues, or technical notes here.

No files, tests, entry points, or concrete API/UI locations are named. Start by tracing the authentication path that identifies the IdP and released attributes, then determine how logging or aggregation should represent attribute names without values. Done means the selected IdP and released attribute names are recorded per authentication, with the required storage, API, UI, migration, and test scope defined.