guys. As mentioned in the title,I wonder whether Shindig implement OAuth2.0 or not? I found an url:http://codereview.appspot.com/3138041/.When I startup the tomcat,however,it throws following exception:
org.apache.http.conn.ConnectTimeoutException: Connect to www.google-analytics.com/www.google-analytics.com/2404:6800:8005:0:0:0:0:61 timed out
I am not sure how to fix this problem and does anyone who encountered this problem before can give me some hints? Thank you in advance!
Yes the 2.5 branch of Shindig does support OAuth 2.0. Shindig contains both a client and provider implementation. The exception you are seeing when starting Tomcat probably has to do with the fact one of the features in Shindig points to that URL and for one reason or another it cannot access the URL. For the most part Shindig should still function properly.
Related
I decorated my Controller class with [Produces("application/json")] to enforce JSON output, but did not help.
Did you find a solution to this issue? I get the same error with the same scenario, but intermittently. The user however get the same error consistently.
How to handle not supported MIME type on azure datactory?
According my experience and I searched a lot, we can't find any solutions to solve the problem. I'm afraid we can't answer you.
So I suggest that you can call the Azure Support for help , maybe they could some more effective suggestions or solution.
You could follow these steps On Portal:
New support request:
Fill the details about you problem:
Then create the request, Azure Support will email or call you later.
Hope this helps.
Thanks Leon. I was able to resolve the issue. My ODATA API (Multi-Tenant App) was in a different Tenant and the Data Factory was in a different Tenant. In my API, the ValidateIssuers was set to true and the ValidIssuers was assigned correctly - array of valid tenants. Even then this was breaking it. I set the ValidateIssuers to false and wrote my custom logic to validate the issuers. This pretty much fixed it. There was another error related to the Audience. The AAD resource property in the Data Factory Linked Service (Connection) should match the ODATA Api AD applications Application ID URI – it is case sensitive. In all these scenarios, the error was always the MIME error which was throwing me off – completely misleading. I had to do some logging in my ODATA Api to get to the actual issue.
I am trying to connect to Jira using OAuth. I have followed this manual and I have created app link in Jira instance and configured it with proper consumer key and public key. When I try to request a token using code from the example I am getting 401 with following message (same for python and perl instance):
oauth_problem=consumer_key_unknown
I am out of ideas what can be wrong. I will appreciate any tips.
Well, I believe that I have configured Application link in the wrong place. I have been somehow navigated to the link wiki/admin/listapplicationlinks.action. Then I accidentally found plugins/servlet/applinks/listApplicationLinks which looked pretty much the same as first but content was different. I have added link to the second location and everything works well now. Sorry for confusion.
I also had this similar error. So I then used different "consumer key"(tried to make this unique) other than the given one in the example manual. After searching a lot in internet about this error, I got to know that as most people are using that same consumer key(given in example manual), a database error occurred due to which this error was thrown.
I have been using Google API Client (gapi.auth.authorize) to handle oAuth and it has been working for months until last night. It started with an error saying something like "_.Uu is not a function" last night, and this morning the api URL becomes inaccessible completely (returning 404):
https://apis.google.com//scs/apps-static//js/k=oz.gapi.en_US.wLUinxMaFvQ.O/m=/exm=client/rt=j/sv=1/d=1/ed=1/am=IQ/rs=AItRSTNDbsyHH46eCqa0_JZmh883Ddz23Q/cb=gapi.loaded_1
Is anyone seeing the same problem? Not sure if Google is making any changes.
I had the same problem.
You need to update the client library and then it will work fine.
The same issue is being discussed on another question. It appears that Google knows about it and is working on it.
Man, what a nightmare!
Can anybody PLEASE point me in the direction of any kind of a proper tutorial or example of how to implement an OAuth2.0 server on Restlet (2.2 or 2.1.1). The only thing resembling a tutorial that I managed to find is this one here, but don't get too excited just yet, because it seems that the code in the framework is being changed more frequently than this tutorial is being updated.
Aside from the above mentioned article, there seems to be a near complete absence of any useful search results on this matter on Google. Surely someone out there must have got this right and is using OAuth2.0 on Restlet?
I did in fact manage to get my OAuth2.0 server as far as to return an access token to me (after spending hours analyzing the source code of the AccessTokenResource.java file), but it seems that it is only validating the client id and not the client secret. Assuming I can sort that out, I am still faced with the task of actually protecting the resources (which should be the job of the OAuthAuthorizer, but that appears to no longer even be present after 2.1.1).
Any help would be greatly appreciated!!
This extension is a work in progress. Please note that OAuth 2.0 has only recently been finalized.
We are currently updating the 2.2 branch to a very recent draft (31). The code has been updated and the documentation indeed needs to follow.
2.2 is still under development and isn't ready for production. We are looking for testers and contributors (code and doc) at this point.
In 2.2 OAuthAuthorizer has been split.
See this issue for additional details:
https://github.com/restlet/restlet-framework-java/pull/644
I'm authenticating with OAuth getting my request token, authorizing, doing POST to get the AccessToken and then pulling my user_timeline.xml
At this point I try and call the destroy api on a particular status id and it returns a 401 unauthorized.
I am able to take the url and the parameters out and call this through Fiddler2 and it works, but using it in a Delphi app with Indy V10 component, doing a POST it's giving this 401 still.
What can I be missing?
Thanks,
david
If I can figure this out this app is good to go, very frustrating.
Please help!
Figured it out. Finally ran a .NET version of code, ran Fiddler2 to see what it did and noticed the Authorization Header. I then had to find a reference to this in regards to the Indy Components to figure it out. You have to add CustomHeaders with a specific format.
You may wanna try my implementation with ICS, supports Unicode as well
http://eden.fm/2011/02/27/twitter-library-for-delphi/