Skip to content

Advertise legacy product names in GetProductIds for CA auto-resolution - #33

Closed
bhillkeyfactor wants to merge 1 commit into
release-1.2from
fix/getproductids-legacy-names-1.2
Closed

bhillkeyfactor wants to merge 1 commit into
release-1.2from
fix/getproductids-legacy-names-1.2

Conversation

@bhillkeyfactor

Copy link
Copy Markdown
Contributor

Summary

  • GetProductIds() only returned the 10 canonical (1.2.0+) product names, not the pre-1.2.0 legacy names still accepted by ValidateProductInfo/GetCertificateType.
  • Command uses GetProductIds() to auto-resolve a CA for a template when no CA is explicitly selected. A Certificate Template still configured with a legacy name (created before the 1.2.0 rename) has no match in that list, so auto-resolution fails with "No CA was found to issue the specified template..." Explicit CA selection still works since it goes through the more lenient ValidateProductInfo.
  • Fix: GetProductIds() now returns the union of canonical names and legacy aliases.

Test plan

  • Updated GetProductIds_ReturnsFullList -> GetProductIds_ReturnsCanonicalAndLegacyNames, asserting both canonical and legacy names are present (17 total).
  • dotnet test - 206/206 passing.

Command uses GetProductIds to auto-resolve a CA for a template when
none is explicitly selected, matching the template's configured
product ID against each CA's advertised list. Existing Certificate
Templates created before the 1.2.0 product rename are still
configured with the old names (e.g. "CSC TrustedSecure EV
Certificate"), which GetProductIds stopped advertising once it was
switched to the canonical list only - auto-resolution then fails
with "No CA was found to issue the specified template" for any
legacy-named template, even though explicit CA selection still
works (that path goes through the more lenient ValidateProductInfo,
which already accepts legacy names).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant