[Feature Request] Add FQDN to the cache key for MI flows.

[neha-bhargava]

Currently SAMI flows use a default value for client id as cache key. This can be a security issue when more than one azure resource with SAMI enabled share a distributed cache.

One of the solution is adding FQDN of the machine to the cache key.

• Add FQDN to cache key for managed identity scenarios.
• Test on resources to validate it resolves the issue.

[bgavrilMS]

@rayluo @neha-bhargava - can you please define FQDN ? How is this computed?

[rayluo]

@rayluo @neha-bhargava - can you please define FQDN ? How is this computed?

There happens to be a getfqdn() helper readily available helper in Python, documented here.

UPDATE: The link above contains the algorithm used to compute the FQDN. Other language likely also has similar helper if they have a similar socket module which is language-agnostic. Even if they don't, I think we do not have to be bullet-proof here. Just fall back to whatever placeholder.