How to filter the Authorization header in ISVA to prevent it from being visible to backend services under a specific junction?
If we need to filter the Authorization header so it's not visible to all services hosted under a specific junction (e.g., to ensure sensitive information in the header, such as credentials or tokens, is not exposed to backend services unnecessarily), how can this be done?
We have checked the options under Junction Management → Identity with the choices: Ignore, Filter, and Supply etc.
Which option should we use for this?
------------------------------
Banu Priya Gopalakrishnan
------------------------------