New-AzConfidentialLedgerCertBasedSecurityPrincipalObject
Create an in-memory object for CertBasedSecurityPrincipal.
Syntax
New-AzConfidentialLedgerCertBasedSecurityPrincipalObject
[-Cert <String>]
[-LedgerRoleName <LedgerRoleName>]
[<CommonParameters>]
Description
Create an in-memory object for CertBasedSecurityPrincipal.
Examples
Example 1: Object creation
New-AzConfidentialLedgerCertBasedSecurityPrincipalObject `
-Cert "-----BEGIN CERTIFICATE-----********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************-----END CERTIFICATE-----" `
-LedgerRoleName "Reader"
Cert
----
-----BEGIN CERTIFICATE-----MIIBsjCCATigAwIBAgIUZWIbyG79TniQLd2UxJuU74tqrKcwCgYIKoZIzj0EAwMwEDEOMAwGA1UEAwwFdXNlcjAwHhc…
Creates an AadBasedSecurityPrincipalObject that may be used for Az.ConfidentialLedger
commands.
Parameters
-Cert
Public key of the user cert (.pem or .cer).
Type: | String |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-LedgerRoleName
LedgerRole associated with the Security Principal of Ledger.
Type: | LedgerRoleName |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Outputs
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Azure PowerShell
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for