I'm making a custom connector with an Elasticserach API and when testing the connector, the following error appearsenter image description here. The URL show me the following message enter image description here
You have posted your token in the body. Your token should be submitted via the header.
Related
Since I'm using Unity Webview as the front end, I have made a redirect URI and registered it when creating a link token. Just following the documentation on: https://plaid.com/docs/link/oauth/#webview
The redirect URI is developed on AWS lambda function, read link_token from cookie, read oauth_state_id from GET query string. Then using the 302 status code and "Location" in Headers to redirect back to Plaid.
I believe it works well because I can get the redirect after I finish operations on Bank account.
But I always get an error: Error: oauth uri does not contain a valid oauth_state_id query parameter. Request ID: juLxa2qy7ZKzZ49
I'm confused about the error, because my Lambda just copied the oauth_state_id from the request to my redirect URI without any change.
And there are some errors shown in the image. errors screenshot
This is an example my redirect URI generated: https://cdn.plaid.com/link/v2/stable/link.html?isWebview=true&token=link-sandbox-02b9e581-c2e1-49d8-b0c0-6ac708535fd1&receivedRedirectUri=https%3A%2F%2Ftdfdfwpj.execute-api.us-west-1.amazonaws.com%2Fdev%2Fplaid-redirect-uri?oauth_state_id=f3d1fe8b-e444-42bb-855a-da5e89a4b796
The error is caused by incorrect use of URLencode, precisely, the whole URL in parameters needs to be encoded.
We are trying to automate in MS teams that will :
Parse json
HTTP Post to API
Get HTTP Response
post comment to the chat using adaptive card.
We created a BOT using power automate, and we created a flow using :
for selected message
parse JSON
HTTP Post to API
Post comment to the chat. using adaptive card
But when we add "response" in power automate using below flow :
for selected message
parse JSON
HTTP Post to API
Response
Parse JSON body (parse body from Response).
Post comment to the chat. using adaptive card
Upon saving, we are getting this error :
Flow save failed with code 'WorkflowUnsupportedSplitOnTriggerForResponseAction' and message 'The workflow with 'Response' action type should not have triggers with 'splitOn' property defined: 'manual'.'.
Please advise the correct flow to rectify above issue ?
Moving from comment's section :
This is by design. You can only add the response flow step after the request action. The response for the trigger is available as properties. Please refer to this thread for a similar issue.
https://powerusers.microsoft.com/t5/Building-Flows/unable-to-use-a-response-action/td-p/378804
The following request does not result in 3DAUTH response (3D secure is enabled):
POST https://test.sagepay.com/gateway/service/vspdirect-register.vsp
VPSProtocol=4.00&Vendor=adventureworks&Currency=GBP&TxType=AUTHENTICATE&VendorTxCode=689359&Amount=158.00&Description=1%20x%20Membership;%20&Basket=1:Membership:1:131.67:26.33:158.00:158.00&CardHolder=Test%20Visa&CardNumber=4929000000006&ExpiryDate=0834&CV2=123&CardType=VISA&BillingFirstnames=Test&BillingSurname=TEst&BillingAddress1=88&BillingCity=london&BillingPostCode=412&BillingCountry=GB&DeliveryFirstnames=Test&DeliverySurname=Test&DeliveryAddress1=88&DeliveryCity=london&DeliveryPostCode=412&DeliveryCountry=GB&ClientIPAddress=10.13.10.191&BrowserJavascriptEnabled=1&BrowserJavaEnabled=1&BrowserColorDepth=24&BrowserScreenHeight=600&BrowserScreenWidth=800&BrowserTZ=0&BrowserAcceptHeader=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3&BrowserLanguage=en-GB&BrowserUserAgent=Mozilla/5.0%20(Windows%20NT%2010.0;%20Win64;%20x64)%20AppleWebKit/537.36%20(KHTML,%20like%20Gecko)%20Chrome/76.0.3809.132%20Safari/537.36&ThreeDSNotificationURL=https://someurl.co.uk/join/callback3DSecure.asp&ChallengeWindowSize=02&CustomerEmail=test#test.com&contains=function(n)%20%7B%0D%0Afor%20(var%20i%20=%200;%20i%20%3C%20this.length;%20i++)%20if%20(this%5Bi%5D%20==%20n)%20return(true);%0D%0Areturn(false);%0D%0A%7D
Tried with BrowserJavascriptEnabled='0', same response.
What am I doing wrong?
I get a successful transaction created is SagePay with 3D response OK
Use CHALLENGE as Cardholder Name and you get the challenge window.
Use STATUS201DS to test the fall back to 3DSv1.
EDIT:
Documentation: DIRECT_Integration_and_Protocol_4_Guidelines.pdf
I am developing an IOT device using smartThings.I am using aws lambda function for getting request and sending responses to the smartThings. I am getting request whenever smartThings app hitting lambda function and sending exact response to that request but still the discover devices are not showing in the smartThings app. Please help me
Refrence link:
https://smartthings.developer.samsung.com/docs/guides/smartthings-schema/smartthings-schema-reference.html#Interaction-types
the first image is the request that i am getting
2nd and 3rd images are the responses that i am getting according to the request
By choosing the correct deviceHandlerType in response the devices started discovering. i.e., "deviceHandlerType": "c2c-rgbw-color-bulb" (reference link for implementing schema for smartThings https://smartthings.developer.samsung.com/develop/guides/smartthings-schema/implement-schema.html)
we can choose deviceHandlerType based on our requirement.
When I try to fetch contacts from gmail, I received this error message:
The page you have requested cannot be displayed. Another site was requesting access to your Google Account, but sent a malformed request. Please contact the site that you were trying to use when you received this message to inform them of the error. A detailed error message follows:
The site "http://url.com" has not been registered.
May I know how to rectify it? Thanks!
Have you tried registering the domain with Google's API?
docs:
https://developers.google.com/accounts/docs/RegistrationForWebAppsAuto#new
resgister url:
https://accounts.google.com/ManageDomains
Also if you are making calls from http and not https you may be seeing problems there too.