Specify certificate based authentication with cert thumbprint

[BrianTJackett]

Suggestion to support specifying the thumbprint of certificate to be used for certificate based authentication. This would be in addition to (or replacing) the option for certificate name. If I'm not mistaken the certificate name could be the same across many different certificates (like a display name) vs. the thumbprint which uniquely identifies the certificate (like an identifier).

Ex. Connect-Graph -ClientId "[clientId]" -TenantId "[tenantId]" -CertificateThumbprint "[certThumbprint]"

[peombwa]

@darrelmiller, as part of this work, should we expose an optional -CertificatePath parameter to Connect-Graph cmdlet? This will be used for scenarios where a customer would like to use a certificate in a different path other than cert:\CurrentUser\My. The default path will still be cert:\CurrentUser\My when -CertificatePath is not specified.

[darrelmiller]

@peombwa I don't have any objections to that plan, but I do wonder if it is necessary. Have you seen examples of other tools doing something similar?

[peombwa]

@darrelmiller, this was in relation to this issue #52 where the customer typically stores their certs in cert:\LocalMachine\My.

Nearly all tools (Azure SDK, AzureAD docs) make the assumption that certs will be stored in cert:\CurrentUser\My. For consistency purposes with other tools, we can maintain the implementation as it is and only use cert:\CurrentUser\My.

[peombwa]

This has been resolved in version 0.1.4.

Install-Module Microsoft.Graph.Beta -RequiredVersion 0.1.4 -Repository GraphPowerShell -Force -AllowClobber

[BrianTJackett]

Confirmed this is working as requested in 0.1.4. Thanks so much for getting this released.