Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No SAN for privatelink address

Open
#12 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, redis
Domain
cloud, networking, security

Research direction

No repository files, tests, or entry points are identified. Start by examining the certificate returned by the Azure Cache for Redis private-link setup and the associated DNS configuration. Done means confirming whether the missing private-link SAN is intended and recording the reasoning or required fix.

Written by the indexing model from the issue text.

Description

Hi, in setting up Azure Cache for Redis, I've noticed that the certificate used by the Redis instance is returning a certificate which has a wildcard for the default *.redis.cache.windows.net domain and an extra one for *.geo.redis.cache.windows.net, however there is not one for the 'default' private link DNS zone *.privatelink.redis.cache.windows.net
Is this intended, if so, what's the reasoning behind this?

Dominant language
PowerShell
Stars
12
Forks
17
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzureCacheForRedis

All issues in Azure/AzureCacheForRedis

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.