Is the below statement accurate? And if so, how can we mitigate the maintainability risks relying on legacy features if Keycloak potentially deprecates them? Will support for external-to-internal token exhange be part of standard functionality within a future Keycloak release?
Keycloak utilizes the OAuth 2.0 Token Exchange (RFC 8693) standard to facilitate exchanging an external token (from a third-party Identity Provider) for an internal Keycloak token. While standard Internal-to-Internal exchange is officially supported as of version 26.2, External-to-Internal exchange is currently handled through a combination of legacy features and standard protocols.