search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.27k stars 21.45k forks source link

Please correct documentation #18253

Closed aravish closed 5 years ago

aravish commented 5 years ago

Self-signed cert needs to be generated by below command for the HDI cluster to provision correctly.

New-SelfSignedCertificate -Subject .contoso100.com -NotAfter $lifetime.AddDays(365) -KeyUsage DigitalSignature, KeyEncipherment -Type SSLServerAuthentication -DnsName ".contoso100.com","contoso100.com"

Errors encountered if not done via above command ,"ErrorCode":"DomainNotFoundInActiveDirectory","ErrorMessage":"Domain contoso100.com not found in the Active Directory."

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Alberto-Vega commented 5 years ago

@aravish Thank you for your feedback! Could you link the URL of the documentation you were following? That way, we can pass your feedback to the appropriate content author.

aravish commented 5 years ago

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-admin-guide-configure-secure-ldap

aravish commented 5 years ago

PowerShell script to be updated with below

$lifetime=Get-Date New-SelfSignedCertificate -Subject .contoso100.com -NotAfter $lifetime.AddDays(365) -KeyUsage DigitalSignature, KeyEncipherment -Type SSLServerAuthentication -DnsName ".contoso100.com","contoso100.com"

messy17 commented 5 years ago

@MarileeTurscak-MSFT please assign to me.

messy17 commented 5 years ago

We reported this issue to the HDI team. They informed us this problem is resolved. Wildcard certificates always begin with an asterisk (*).

please-close

VolodymyrMolodets commented 4 years ago

It is worth mentioning that even if you do generate self-signed certificate using the command above, you can still face the very same error if the vnet you are deploying to is not configured with the IP-addresses of DNS servers for AADDS. I ran into this even though I had vnet peering with AADDS vnet configured.