Add port with IP address CIDR as option for tenant identification in configuration
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
With SIP2-133 it was identified a self-check vendor (Meescan) which does not allocate an IP address for each tenant. We therefore need a different way of identifying tenants in this case.
If we combine an additional item, port number, with an IP address CIDR range, and make this a configuration option, multiple tenants can be identified for a single IP range, allowing us to support Meescan. There are two steps that need to be completed to make this change: 1) allow for an additional optional property in the existing SIP configuration for port number, and 2) modify the tenant identification logic to check for this additional port option for a given IP address in a request.
Hi , The Jira was spilled because of the delay in PR review. The work will be completed in Sprint 198.
Tetiana Gusar August 20, 2024 at 2:38 PM
, as discussed today during retro, please add some reasons that led to spillover for this Jira (lower estimations, overcommitment, some dependency, delays with PR review etc.)
With SIP2-133 it was identified a self-check vendor (Meescan) which does not allocate an IP address for each tenant. We therefore need a different way of identifying tenants in this case.
If we combine an additional item, port number, with an IP address CIDR range, and make this a configuration option, multiple tenants can be identified for a single IP range, allowing us to support Meescan. There are two steps that need to be completed to make this change: 1) allow for an additional optional property in the existing SIP configuration for port number, and 2) modify the tenant identification logic to check for this additional port option for a given IP address in a request.