Is there any expiry date of the security token present in the URL which I got through:
Amplify.Storage.getUrl(
"ExampleKey",
result -> Log.i("MyAmplifyApp", "Successfully generated: " + result.getUrl()),
error -> Log.e("MyAmplifyApp", "URL generation failure", error)
);
I'm asking this because I want to hardcode the URL in my post model of graphql schema
Second question: is it good to hardcode the URL? I'm worried because recently the s3 object URL format got deprecated.
Update (September 23, 2020) – Over the last year, we’ve heard feedback from many customers who have asked us to extend the deprecation date. Based on this feedback we have decided to delay the deprecation of path-style URLs to ensure that customers have the time that they need to transition to virtual hosted-style URLs.
Like this one day, virtual hosted-style URLs might be deprecated
Related
I am using Paypal api for my Django website.I am able to make payment but don't know how to get payment response from paypal server as either True or False.
Without knowing what you are currently doing, I can only share the best solution.
Create two routes, one for 'Create Order' and 'Capture Order', documented here. These routes should return/output only JSON data (no HTML or text).
Pair those two routes with the following approval flow: https://developer.paypal.com/demo/checkout/#/pattern/server
In the Capture Order route, before returning the JSON, examine the response for a PayPal transaction ID in the payments object and store this information in your database. If there is a new transaction ID, its status should be 'COMPLETED' or 'PENDING'. In the latter case, flag it for manual review in PayPal.com
Last year I was building an application to create my own YT dashboard.
It was based only the code of a tutorial
They basically authenticate a user via OAuth and send requests to get channel data or playlists of the authenticated user.
I was trying out both the original tutorial app and my own (after a few dormant months) and they suddenly don't work anymore.
Meaning: I can authenticate on both, but on the original version I get a 403 error telling me: "The request is missing a valid API key." (on requesting channel data)
This is confusing because the API key is never used because only the OAuth client id was necessary.
And on my own fancy version, I get a 403 error telling me that I've exceeded my getting started quota. (on requesting the users playlists)
Looking at my quota page:
I can see, that queries per day (why is it there twice?) is somehow set to 0.
Perhaps creating a new OAuth 2.0 Client ID or a new API key would solve these errors, as was suggested in another post.
But since I'm planning to use the YT Data API in a real project soon and want to prevent this from ever happening I would like to understand what was going on. Why the daily quota limit is suddenly turned to 0 and how to go about it when that happens.
Or at least how to contact google about it.
Perhaps some of you have some insights.
UPDATE:
I've just found this post reporting, that after 90 inactive days, the quota is automatically set to 0.
Now I created a new OAuth Client Id and replaced the constant in my code. Nothing changed so far. Perhaps I have to wait 24h. Or perhaps I have to fill out this form which apparently can lead to months of back and forth email nonsense. I sure hope not.
It seemed the only viable option was to create a new project with new credentials.
(And one should not forget that the YT Data API has to be enabled again for the new project.)
After processing the payment, control is not directing back to our site(x_relay_url) from https://test.authorize.net/gateway/transact.dll.
The URL mentioned in the x_relay_url cannot be accessed directly it requires session id and other details to access it which was passed to Authorize net page using merchantDefinedData variables.
I checked the following article also but our URL seems to be fine and we checked our code there is nothing wrong in that.
I tried multiple URLs in "x_relay_url" but nothing seems to be working.
Any help is appreciated.
Error Message:
An error occurred while trying to report this transaction to the
merchant. An e-mail has been sent to the merchant informing them of
the error. The following is the result of the attempt to charge your
credit card.
This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.
I am trying to collect visitor posts from the page of a political party. Even though I can collect the statuses posted from the political party itself, when I request a token for visitor_posts, I get the following error message:
{
"error": {
"code": 1,
"message": "Please reduce the amount of data you're asking for, then retry your request"
}
}
When I then add a limit, I get the same error message, even when I set the limit as 1, 10, or 100. After googling around, people then suggested to add a since/until, since there would be such a high number of visitor posts. However, when I tried that, it also did not work. Has Facebook changed its API to block this kind of collection?
Thanks in advance.
The endpoint [page]/visitor_posts is still functioning correctly, though there are prerequisites for calling it. Assuming you are a page management app, your access token must have manage_pages and pages_show_list scopes.
It isn't necessary for you to use a page access token to make this call and the request can be made with a user access token. It's also not necessary to have any permissions or specific roles on the page you are querying.
Since you are having issues with too much data being returned, although including a limit didn't help, you may help their query engine out by providing a since parameter. This is a filter for posts since a certain unix (seconds) timestamp, example using 12:00 AM UTC today:
[page]/visitor_posts?since=1523318400
Having a task to get the details of password last update date to calculate remaining days for expiring.
I tried using Claim uri http://wso2.org/claims/identity/failedLoginAttempts and http://wso2.org/claims/identity/accountLocked to get the details on failed attempts and status of the account. which worked as expected, but to get the password last updated date, i require a claim uri and the attribute to fetch the field value.
Could you please help in understanding this?
There is claim uri that is defined as http://wso2.org/claims/passwordTimestamp But i do not think it has been used in Identity Server. This is latest code of identity management listener that implements these functions. I can not find usage of this claim