[BUG] Cannot bind parameter 'Credentials'. Used documentation

[200mpg]

Hi,

I really need help with this. Cannot find information anywhere and boss is hounding me. You are my only hope

 

Reporting an Issue or Missing Feature

Secret not passing through connect-pnponline

Expected behavior

Please describe what output you expect to see from the PnP PowerShell Cmdlets

Connected to Pnp or similar. See reproduction below

Actual behavior

Please describe what you see instead. Please provide samples of output or screenshots.

See preproduction below

Steps to reproduce behavior

Setup secret store, added secret name and value, configured store for no authentication. Run the below command from the documentation:

Receive the below:

What is the version of the Cmdlet module you are running?

(you can retrieve this by executing Get-Module -Name "PnP.PowerShell" -ListAvailable)

2.5.0

Which operating system/environment are you running PnP PowerShell on?

• [X ] Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[200mpg]

@veronicageek Have you been successful in connecting to pnponline using secret stored in secret vault?

[veronicageek]

Yes

[ToddKlindt]

What kind of object is your secret? 200mpg's secret is a securestring. The error they're getting is that it can't be converted to a Credential. Is your secret a Credential?

[200mpg]

@veronicageek Thank you for the reply. Per the PnP powershell documentation, the PnP app is registered in our tenant, added the generated secret string to a new secret in a local vault. Calling the secret still throws the below:

Is you're secret string a secure string?