I had a question in terms of running the ATestnetConsumer.sol through remix on the polygon chain. I was able to run the oracle.sol with no issues and copy down the contract address, and creating a job with it. But when I run the consumer.sol, i get an error for "Internal JSON-RPC error code: -32000" is there an exact issue that can be tracked down to?
The setPublicChainlinkToken() function in the constructor that has no parameters is only configured to automatically set the address of the LINK token for Ethereum chains, any other EVM chains need to explicitly pass in the token address. Please update it to pass in the address of the LINK token on Mumbai as a parameter, and try again.
setChainlinkToken(0x326C977E6efc84E512bB9C30f76E30c160eD06FB);
Related
as the title already implies my RestAPI does not forward the user information of the authorized client to my lambda function. I tried with a rust lambda function (see the issue here), but it turned out, a nodejs implementation has the same problem. I have posted my cdk setup in the above issue and i bet there is a configuration mistake i made, but just cannot find.
I checked that you need to be authroized in the first place (which works, as the gateway returns "unauthorized" in that case). But whatever i tried so far, the context.identity field is always empty/null.
Any help appreciated!
I'm currently developing an application where holders can see historical data of their NFT's. All code is in place, but I'm still looking for a way to securely verify their ownership of a certain NFT.
There is the possibility to extend one of the dApp examples in the Elrond docs, but I'm not that familiair to React or NodeJS, so I'm trying to build this in PHP.
One thing I came across, is the login via Hooks, as used by the Maiar Exchange.
https://docs.elrond.com/wallet/webhooks/#login-hook
However, the Callback URL can be accessed manually by users, so this can give people Unauthorized access to my application.
Now, there is an undocumented extra parameter token I can pass to the Login hook (as used by Maiar Exchange). I know I can fetch a valid token by sending a POST request to 'https://id.maiar.com/api/v1/login/init'. This will give back a token I can append to the Callback URL. By doing so, the Callback URL will receive an appended signature parameter. I feel like I'm almost there, but the question is: How can I interpret this signature and how can I use this signature to verify if the returned response was valid and belongs to the given token/address? How was this signature is generated?
Also, I feel like it would be very nice if there was some sort of OAuth implementation for Elrond, but since it isn't there, I'm trying this approach.
import requests
params = {
'apiKey': 'hidden',
'author_id': '36573126000'
}
def main():
r = requests.get('https://api.elsevier.com/content/author', params=params)
print(r.text)
main()
I'm unable to communicate with the API, as it's returning the following error:
<service-error><status><statusCode>AUTHORIZATION_ERROR</statusCode><statusText>The requestor is not authorized to access the requested view or fields of the resource</statusText></status></service-error>
What is / are the issue(s), and how can I resolve this?
There can be two issues that can cause this:
Your API Key does not have the correct level of entitlement to access that resource
You are attempting to access this resource outside of your institutional network and will need an Institutional Token to enable this.
Both can be resolved by contacting Elsevier Support at the following form:
https://service.elsevier.com/app/contact/supporthub/researchproductsapis/
This issue is usually because your current connection/IP is not the same as the one you used to create your Scopus Account; which is usually the Institutional Connection that has been granted access to Scopus.
So if there is a need to access Scopus outside that specific IP (institutional IP), then you need to setup a remote VPN proxy for yourself or Inst tokens might work as well.
Read below for clarity:
The Scopus API recognizes you as a member of your institution via IP
range. For working remotely, Scopus can also grant InstTokens. Thus
one of three things needs to happen:
You are in your instition’s network
You use your instition’s VPN
You use an InstToken
Option 1 is easy and the most common.
Option 2 might require you to additionally set a proxy. You can do so
in the configuration file.
Option 3 is rare. If you have an InstToken, please provide it during
the setup. Alternatively, add it
to the configuration file manually. You may also set the InstToken via
insttoken=”XYZ” in any class. This is the preferred solution if you
possess multiple keys.
Please Note: These suggestions are listed under pybliometrics python wrapper class documentation. However, this issue of accessing Scopus API must be the same regardless of the language and these suggestions might work.
Hey I am tryng to create a poap-booth for my event on decentraland.
Using the following documentation I am linking the booth in the game.ts SDK to the poapHandler.ts
This would allow me to create a token to give out at events when connected to the POAPBOOTH entity
I need help as to connect to firebase using cloudfirestore which is used to store addresses and give out the token I need to set up two api endpoints using postman
https://github.com/decentraland-scenes/POAP-Booth
https://decentraland.org/blog/tutorials/servers-part-2/
the GET function works with a success message of 200
However the POST method for signatures does not with 500 error
I am facing this error sometimes (not always). I create a resource and a method in an API Gateway function. Then I map it to a Lambda function. On testing it there itself, everything works fine.
Now I add a custom authorization function to the method. Now, if I test it there,
If I do not provide the Authorization header, it works (since it is not deployed yet. After deployment, it would require the Auth header)
If I, however, provide the Authorization token, I get the error:
The request signature we calculated does not match the signature you
provided. Check your AWS Secret Access Key and signing method. Consult
the service documentation for details.\n\nThe Canonical String for
this request should have
been\n'POST\n/2015-03-31/functions/arn%3Aaws%3Alambda%3Aus-eas
More details: The lambda function belonging to this method was deleted. Then I re-created the function with the same name. And noticed that the method was deleted when the API was deployed. So I re-created the mapping and mapped it to the Lambda function. Since, then I am facing this issue. I am sure if I change the name of the Lambda, it might fix the issue. But I think it's a bug with AWS and not at my end. Need to clarify if there is anything I am doing wrong ?
It looks like the currently deployed version of the API is forwarding the Authorization header from the method request to the integration request (Lambda). If you are trying to fix the current state of your API, then I suggest removing the Authorization header from the method request, which will also remove it from the integration request. This should fix the Lambda signature errors.
If you're trying to use the custom authorizer on a method, you don't need to set up the Authorization header in the method request. You just need to set the authorizer identity source as 'method.request.header.Authorization'