PAYEE_ACCOUNT_NOT_VERIFIED - PayPal Problem - rest

I have a question about users who set up a PayPal account but haven't verified it. In our system, they can start selling, but PayPal does not allow customers to buy products until the seller verifies the account(?). Is it possible to remove this limit or anything to do with it from the PayPal website so that people who set up a new account can start selling immediately and, for example, verify their account later? The question is for this error: PAYEE_ACCOUNT_NOT_VERIFIED
This is what we send (from database):
{"intent": "CAPTURE", "application_context": {"cancel_url": "XX," return_url ":"XX"}," purchase_units " : [{"invoice_id": "11-04033241 \ / 12 \ / 2021 \ / 87", "items": [{"name": "Y", "unit_amount": {"currency_code": " AUD "," value ":" 38.50 "}," quantity ":" 1 "," category ":" PHYSICAL_GOODS "}]," amount ": {" value ":" 53.50 "," currency_code ":" AUD " , "breakdown": {"item_total": {"value": "38.50", "currency_code": "AUD"}, "shipping": {"value": "15.00", "currency_code": "AUD"}} }, "payee": {"merchant_id": "XX"}, "payment_instruction": {"disbursement_mode": "INSTANT", "platform_fees": [{"amount": {"currency_code": "AUD", "value ":" 3.50 "}}]," payee ": {" merchant_id ":" XX "}}," shipping ": {" address ": {" address_line_1 ":" X "," address_line_2 ":" " , "admin_area_1": "XX", "admin_area_2": "XX", "postal_code": "XX", " country_code ":" AU "}}}]}
This is the answer from PayPal:
{"name": "NOT_AUTHORIZED", "details": [{"issue": "PAYEE_ACCOUNT_NOT_VERIFIED", "description": "Payee has not verified their account with PayPal. Your current setup requires the 'payee' to have an account with PayPal before you can process transactions on their behalf. "}]," Message ":" Authorization failed due to insufficient permissions. "," Debug_id ":" aef1250ffb618 "," links ": [{" href ":" https: / /developer.paypal.com/docs/api/orders/v2/#error-PAYEE_ACCOUNT_NOT_VERIFIED","rel":"information_link","method":"GET "}]}

The payee account with the merchant_id you specified needs to confirm their primary email in paypal.com here. Re-send a verification email as needed, which will have a link to verify it.
If this is sandbox, the same can be done in a sandbox account but sandbox never sends "real" emails. Instead go to the Notifications left nav tab in the developer dashboard, to read "emails" for the sandbox accounts that belong to that developer dashboard login.

Related

MongoDB Replica Set - The value of parameter linuxConfiguration.ssh.publicKeys.keyData is invalid

This is concerning the Azure Deployment Template for a MongoDB Replica Set defined here mongodb-replica-set-centos.
When I run the recommended deployment commands to deploy the replica set, namely
az group create --name <resource-group-name> --location <resource-group-location> # Use this command when you need to create a new resource group for your deployment.
az deployment group create --resource-group <my-resource-group> --template-uri https://raw.githubusercontent.com/migr8/AzureDeploymentTemplates/main/mongo/mongodb-replica-set-centos/azuredeploy.json
where the resource group is already set up. I receive the following error:
{
"status": "Failed",
"error": {
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "Conflict",
"message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"InvalidParameter\\\",\\r\\n \\\"message\\\": \\\"The value of parameter linuxConfiguration.ssh.publicKeys.keyData is invalid.\\\",\\r\\n \\\"target\\\": \\\"linuxConfiguration.ssh.publicKeys.keyData\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"
},
{
"code": "Conflict",
"message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"InvalidParameter\\\",\\r\\n \\\"message\\\": \\\"The value of parameter linuxConfiguration.ssh.publicKeys.keyData is invalid.\\\",\\r\\n \\\"target\\\": \\\"linuxConfiguration.ssh.publicKeys.keyData\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"
}
]
}
}
The problem field is in both primary-resources.json and secondary-resources.json appears to be
"variables": {
"subnetRef": "[resourceId('Microsoft.Network/virtualNetworks/subnets', parameters('subnet').vnet, parameters('subnet').name)]",
"securityGroupName": "[concat(parameters('namespace'), parameters('vmbasename'), 'nsg')]",
"linuxConfiguration": {
"disablePasswordAuthentication": true,
"ssh": {
"publicKeys": [
{
"path": "[concat('/home/', parameters('adminUsername'), '/.ssh/authorized_keys')]",
"keyData": "[parameters('adminPasswordOrKey')]"
}
]
}
}
},
And ascociated with the variable adminPasswordOrKey. I have tried changing this to be both standard passwords and SSH keys of varying bit-depth, no luck...
How can I fix this?
Repro steps
Run az group create --name <resource-group-name> --location <resource-group-location> where resource group exists.
Run az deployment group create --resource-group <my-resource-group> --template-uri https://raw.githubusercontent.com/migr8/AzureDeploymentTemplates/main/mongo/mongodb-replica-set-centos/azuredeploy.json and step through the prompts
Enter the relevant in formation.
Further Investigation
I have just seen this answer (https://stackoverflow.com/a/60860498/626442) saying specifically that
Note: Please note that the only allowed path is /home//.ssh/authorized_keys due to a limitation of Azure.
I have changed this value of the path, no joy, same error. :'[
You forgot to pass parameters in az deployment group create .... --parameters azuredeploy.parameters.json. You can download azuredeploy.parameters.json and change values as needed. See https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorial-use-parameter-file?tabs=azure-cli#deploy-template for details.
Specifically the error in the question complains about adminUsername parameter being empty. Bear in mind this user name is also being used in the home directory path, so limit yourself to lowcase ASCII a-z, numbers, underscore. No spaces, not special characters, no utf.
Not related to the error, but be aware these necromancers use mongo 3.2 which was buried 4 years ago: https://www.mongodb.com/support-policy/lifecycles. Considering they open it wide to the internet you may have way more problems if you actually deploy it.
UPDATE
An example of the parameters I used:
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"adminUsername": {
"value": "yellow"
},
"mongoAdminUsername": {
"value": "phrase"
},
"mongoAdminPassword": {
"value": "settle#SING"
},
"secondaryNodeCount": {
"value": 2
},
"sizeOfDataDiskInGB": {
"value": 2
},
"dnsNamePrefix": {
"value": "written"
},
"centOsVersion": {
"value": "7.7"
},
"primaryNodeVmSize": {
"value": "Standard_D1_v2"
},
"secondaryNodeVmSize": {
"value": "Standard_D1_v2"
},
"zabbixServerIPAddress": {
"value": "Null"
},
"adminPasswordOrKey": {
"value": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDdNRTU0XF3xazhhDmwXXWGG7wp4AaQC1r89K7sZFRXp9VSUtydV59DHr67mV5/0DWI5Co1yWK713QJ00BPlBIHNMNLuoBBq8IkOx8fBZF1g9YFm5Zy4ay+CF4WgDITAsyxhKvUWL6jwG5M3XIdVYm49K+EFOCWSSaNtCk8tHhi3v6/5HFkwc2r0UL/WWWbbt5AmpJ8QOCDk/x+XcgCjP9vE5jYYGsFz9F6V1FdOpjVfDwi13Ibivj/w2wOZh2lQGskC+qDjd2upK13+RfWYHY3rr+ulNRPckHRhOqmZ2vlUapO4T0X9mM6ugSh1FprLP5nHdVCUls2yw4BAcSoM9NMiyafE56Xkp9h3bTAfx5Ufpe5mjwQp+j15np1pVpwDaEgk7ZeaPoZPhbalpvZGyg9KiKfs9+KUYHfGklIOHKJ3RUoPE286rg1U4LGswil5RARRSf86kBBHXaIPxy1X0N6QryeWhk0aM6LWEdl7mVbQksa7ilANnsaVMl7FSdY/Cc="
}
}
}
DANGER: It will deploy publicly accessible mongodb replica set with publicly accessible credentials, so please delete the resources as soon as you are happy with testing/debugging
This is how deployment looks like on the portal:

Can't build customise Slack notifications

After much research, I discovered this .sh script, which allows me to send a very simple personalized notification to a Slack channel (I failed to send it to a particular member).
The problem, which I am facing, is that of formatting the message of the notification. The tags offered on the Slack site to format the notification do not work correctly (that I do not know how to use them!).
The notification must be built "from scratch" at the end of each execution of the Rundeck job.
Rundeck's "On Failure" and "On Success" notifications are not suitable for users.
This the sh script :
#!/bin/bash
​#Usage: slackpost <channel> <message>
slackhost="https://hooks.slack.com/services"
token="XXXXXXXXXX/XXXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXX"
slack_username="Someone-who-loves-you"
slack_icon="smile"​
channel=$1
if [[ $channel == "" ]]
then
echo "No channel specified"
exit 1
fi
text="$2"
if [[ $text == "" ]]
then
echo "No text specified"
exit 1
fi
escapedText=$(echo $text | sed 's/"/\"/g' | sed "s/'/\'/g" )
json="{\"channel\": \"#$channel\", \"username\":\"${slack_username}\", \"icon_emoji\":\":${slack_icon}:\", \"text\": \"$escapedText\"}"
curl -s -d "payload=$json" "$slackhost/$token"
The variable $text is filled with the content of a .txt file (myFileText):
myFileText content is as follows:
text="",
{
blocks=[
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Hello world! <#UNVD64N02> :tada: \n\n - a \n-b"
}
}
]
}
{
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Hello, Assistant to the Regional Manager John Doe! *Martin Scott* wants to know where you'd like to take the Paper Company investors to dinner tonight.\n\n *Please select a restaurant:*"
}
}
]
}
The .sh script is run as follows:
sh slack_post.sh "channel-receiving-the-notification" "$(< myFileText)"
As result I have :
invalid_payload
Any idea could be helpful.

Unable to create kafka connector using REST API

I am trying to run Kafka workers in distributed mode. Unlike standalone mode, we cannot pass the connector property file while starting the worker in distributed mode. In Distributed mode, workers are started separately and we deploy and manage the connectors on those workers using REST API
Reference Link - https://docs.confluent.io/current/connect/managing/configuring.html#connect-managing-distributed-mode
I tried building a connector by passing the below values in curl command and execued it
curl -X POST -H "Content-Type: application/json" --data '{"name":"sailpointdb","connector.class":"io.confluent.connect.jdbc.JdbcSourceConnector","tasks.max":"1","connection.password " : " abc","connection.url " : "jdbc:mysql://localhost:3306/db","connection.user " : "abc" ,"query" : " SELECT * FROM (SELECT NAME, FROM_UNIXTIME(completed/1000) AS
TASKFAILEDON FROM abc WHERE COMPLETION_STATUS = 'Error') as A","mode" : " timestamp","timestamp.column.name" : "TASKFAILEDON","topic.prefix" : "dbevents","validate.non.null" : "false" }}' http://localhost:8089/connectors/
I am getting below error - curl: (3) URL using bad/illegal format or missing URL
Please let me know what is wrong with the above curl statement, am i missing anything here
You had an extra closing curly brace in your JSON which won't help
If you're POSTing to /connectors you need the name and config root level elements. But, I recommend using PUT /config because you can re-run it to update the config if you need to
Try this:
curl -X PUT -H "Content-Type:application/json" \
http://localhost:8089/connectors/source-jdbc-sailpointdb-00/config \
-d '{
"connector.class": "io.confluent.connect.jdbc.JdbcSourceConnector",
"tasks.max": "1",
"connection.password ": " abc",
"connection.url ": "jdbc:mysql://localhost:3306/db",
"connection.user ": "abc",
"query": " SELECT * FROM (SELECT NAME, FROM_UNIXTIME(completed/1000) AS TASKFAILEDON FROM abc WHERE COMPLETION_STATUS = 'Error') as A",
"mode": " timestamp",
"timestamp.column.name": "TASKFAILEDON",
"topic.prefix": "dbevents",
"validate.non.null": "false"
}'

Uploading a CSV file, distorted characters

I am having a problem when uploading a csv file through the following query,
COPY adwords_initial("Account",
"Week",
"Campaign",
"Keyword",
"Ad group",
"Keyword state",
"Match type",
"Max. CPC",
"Clicks",
"Impressions",
"Cost",
"Avg. position",
"Ad group state",
"Campaign state",
"Status",
"Qual. score (hist.)",
"Expected clickthrough rate (hist.)",
"Ad relevance (hist.)",
"Landing page experience (hist.)",
"First page CPC",
"First position CPC",
"Top of page CPC",
"Bounce rate","Pages / session",
"Avg. session duration (seconds)",
"% new sessions",
"Search Exact match IS",
"Search Lost IS (rank)",
"Search Impr. share",
"Conversions",
"Conv. rate")
FROM 'C:\Users\iantu\Desktop\Performance Marketing\Report inputs\input.csv'
DELIMITER ',' CSV HEADER encoding 'windows-1251';
Characters in French do not translate accordingly as an example
in keyword the original file has +connectivité +IoT
in keyword the postgresql file has +connectivitй +IoT
Do settings have to be changed within my application?
I should also mention that I then export this using the following query, however, the data as can be seen is already corrupted within the database.
COPY (SELECT * FROM adwords_initial) TO 'C:\Users\iantu\Desktop\Performance Marketing\Report Outputs\in between workflow.csv' WITH CSV HEADER;
Use latin1 as encoding:
COPY adwords_initial("Account",
"Week",
"Campaign",
"Keyword",
"Ad group",
"Keyword state",
"Match type",
"Max. CPC",
"Clicks",
"Impressions",
"Cost",
"Avg. position",
"Ad group state",
"Campaign state",
"Status",
"Qual. score (hist.)",
"Expected clickthrough rate (hist.)",
"Ad relevance (hist.)",
"Landing page experience (hist.)",
"First page CPC",
"First position CPC",
"Top of page CPC",
"Bounce rate","Pages / session",
"Avg. session duration (seconds)",
"% new sessions",
"Search Exact match IS",
"Search Lost IS (rank)",
"Search Impr. share",
"Conversions",
"Conv. rate")
FROM 'C:\Users\iantu\Desktop\Performance Marketing\Report inputs\input.csv'
DELIMITER ',' CSV HEADER encoding 'latin1';

New-AzureRmResourceGroupDeployment command giving error

When I run the New-AzureRmResourceGroupDeployment and pass a JSON parameter file, I get the below error:
New-AzureRmResourceGroupDeployment : 2:29:31 PM - Resource Microsoft.Sql/servers 'qsservername' failed with message '{
"code": "15021",
"message": "Invalid value given for parameter Login. Specify a valid parameter value.",
"target": null,
"details": [
{
"code": "15021",
"message": "Invalid value given for parameter Login. Specify a valid parameter value.",
"target": null,
"severity": "16"
}
],
"innererror": []
}'
At M:\Azure\Azure Scripts\Something\somethingdeploy.psm1:63 char:4
+ New-AzureRmResourceGroupDeployment -ResourceGroupName $resourceGro ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-AzureRmResourceGroupDeployment], Exception
+ FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet
However, when I run the same command but pass the parameters instead of the file, it works fine. any ideas what I may be missing?
For me, this error happened when I tried to run ARM templates with the existing SQL Azure instance resource. The problem was that in the template I specified a DB username which didn't match the admin username of the existing instance. It's ok to update the password, but the username has to remain the same for the life of SQL Azure instance,