[IGNITE-20814] Replace AuthorizationHeaderFilter with own implementation of SecurityFilter

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: rest
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Ivan Gagarkin
• Reporter: Ivan Gagarkin
• Created: 08/Nov/23 15:26
• Updated: 10/Nov/23 12:25
• Resolved: 10/Nov/23 12:25

Description

Current Behavior: We're currently injecting an empty Authorization header in requests lacking one, as Micronaut filters out requests without authentication headers. This is handled by the AuthorizationHeaderFilter.

Problem: This workaround is not ideal and could lead to maintainability issues.

Proposed Solution: Develop a custom SecurityFilter that:

• Checks whether authentication is enabled.
• Forwards requests to io.micronaut.security.filters.SecurityFilter if authentication is required.
• Allows requests to proceed without authentication if it's not required.

Objective: To replace the AuthorizationHeaderFilter with a more robust and maintainable custom SecurityFilter implementation.

Issue Links

• links to: GitHub Pull Request #2819