Selectively providing mutual transport layer security using alternative server names
AssigneeInternational Business Machines Corporation
InventorsZvi Cahana, Etai Lev-Ran, Idan Zach, Shriram Rajagopalan
Life of this patent
Estimating the term…
Abstract
Examples of techniques for selectively providing mTLS using alternative server names are described herein. An example system includes a processor to generate an alternative server name in response to detecting a legacy indicator. The processor is to also associate the alternative server name with an address of a pod. The processor is to further configure a proxy associated with the pod to selectively provide mutual transport layer security (mTLS) based on the alternative server name.
Claims20
A system, comprising a processor to:
- generate an alternative server name in response to detecting a legacy indicator and associate the alternative server name with an address of a pod;
- and
- configure a proxy associated with the pod to selectively provide mutual transport layer security (mTLS) based on the alternative server name.
A computer-implemented method, comprising:
- detecting, via a processor, a legacy indicator;
- modifying, via the processor, a uniform resource location (URL) of a pod to use an alternative server name;
- and
- configuring a proxy associated with the pod to disable mutual transport layer security (mTLS) in response to receiving the alternative server name.
A computer program product for selectively providing mutual transport layer security (mTLS), the computer program product comprising a computer-readable storage medium having program code embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the program code executable by a processor to cause the processor to:
- monitor a plurality of manifests for a plurality of legacy indicators;
- detect a legacy indicator associated with at least one legacy client in at least one of the plurality of manifests;
- generate an alternative server name in response to detecting the legacy indicator;
- associate the alternative server name with an address of a pod;
- and
- configure a proxy associated with the pod to disable a service in response to receiving a server name indicator comprising the alternative server name from a legacy client.
Dependencies are inferred from the claim text.