Is your feature request related to a problem? Please describe.
API Keys created through Portal have a predefined set of metadata fields with no ability for users to add additional metadata as part of the creation process. Additionally, the headersFromMetadata configuration in the associated AuthConfig includes a static definition of what metadata is included as headers.
Describe the solution you'd like
When creating an API Key through the developer portal, we would like to allow users to attach additional metadata in the form of key=value to the API Key. This information should then be available to access logging and upstream header passing. Instead of passing all metadata from the API Key, allow the portal admin to configure which headers should be included in the headersFromMetadata config in AuthConfig.
Is your feature request related to a problem? Please describe. API Keys created through Portal have a predefined set of metadata fields with no ability for users to add additional metadata as part of the creation process. Additionally, the headersFromMetadata configuration in the associated AuthConfig includes a static definition of what metadata is included as headers.
Describe the solution you'd like When creating an API Key through the developer portal, we would like to allow users to attach additional metadata in the form of key=value to the API Key. This information should then be available to access logging and upstream header passing. Instead of passing all metadata from the API Key, allow the portal admin to configure which headers should be included in the headersFromMetadata config in AuthConfig.