username:passwor<\/code>d. In the example below we will add the username and password as well in the URL, but that is only for testing purposes:<\/p>\n\n\n\ncurl -u \"username:password\" https:\/\/httpbin.org\/basic-auth\/username\/password\n\n# returns on succesfull authentication\n{\n \"authenticated\": true,\n \"user\": \"username\"\n}<\/pre>\n\n\n\nWhen using the PowerShell method, Invoke-WebRequest<\/code>, we first need to create a credential object. You can ask the user to input the credentials, with the Get-Credential<\/code> cmdlet, but when you want to store the credentials in your script, you will need to convert them to a secure string first:<\/p>\n\n\n\n# Get the credentials from the user\n$Credentials = Get-Credential -UserName \"username\" -Message \"Enter your password\"\n\n# Or store the credentials in the script\n$Password = ConvertTo-SecureString \"password\" -AsPlainText -Force\n$Credentials = New-Object System.Management.Automation.PSCredential (\"username\", $Password)\n\nInvoke-WebRequest -Uri \"https:\/\/httpbin.org\/basic-auth\/username\/password\" -Credential $Credentials\n<\/pre>\n\n\n\n<\/span>Wrapping Up<\/span><\/h2>\n\n\n\nIt’s a good thing that Microsoft removed the cURL alias in PowerShell 7, because eventhough cURL and Invoke-WebRequest may look similar, cURL has a lot more capabilites. If you are creating scripts that are going to run on other machines, then you can use the command curl.exe<\/code> to be sure that cURL is used instead of Invoke-WebRequest.<\/p>\n\n\n\nHope you liked this article, if you have any questions, just drop a comment below.<\/p>\n