2-legged | 易学教程

Getting Forge 2-legged authentication using Cross request

阅读更多关于 Getting Forge 2-legged authentication using Cross request

问题 I'm trying to create a simple html page to display a uploaded model to forge. For initialize the forge viewer it required the access-token. For request the access token I'm using the 2-legged oAuth on a Cross request(because I'm making the POST on different domain).But it keep getting error "No 'Access-Control-Allow-Origin' header is present on the requested resource". Please some one can tell me what should I do to get the acces-token successfully. 回答1: As you noticed, you cannot obtain a

Getting Forge 2-legged authentication using Cross request

阅读更多关于 Getting Forge 2-legged authentication using Cross request

2-legged OAuth with google-api-java-client

阅读更多关于 2-legged OAuth with google-api-java-client

问题 Does anyone know how to use 2-legged OAuth with google-api-java-client? I'm trying to access the Google Apps Provisioning API to get the list of users for a particular domain. The following does not work HttpTransport transport = GoogleTransport.create(); GoogleHeaders headers = (GoogleHeaders) transport.defaultHeaders; headers.setApplicationName(APPLICATION_NAME); headers.gdataVersion = GDATA_VERSION; OAuthHmacSigner signer = new OAuthHmacSigner(); signer.clientSharedSecret = CONSUMER_SECRET

oAuth in PHP to make 2 legged request

阅读更多关于 oAuth in PHP to make 2 legged request

问题 I am currently stuck trying to make requests to a service's api using a 2 legged oAuth request using PHP. I am using the PHP library found here: http://code.google.com/p/oauth-php/ and there seems to be absolutely no documentation anywhere online for using this library for a 2 legged request. So currently from the service I have the following details: $consumer_key - needs to be an empty string $consumer_secret - needs to be an empty string $access_token - my login name $access_token_secret -

Has anybody implemented 2 Legged OAuth using DNOA?

阅读更多关于 Has anybody implemented 2 Legged OAuth using DNOA?

问题 I am trying to create an Authentication Module in CSharp where I need to verify the Signature from the request using DotNetOpenAuth(DNOA) Library for 2 Legged OAuth which only has consumer Key and a Secret. If you have any sample implementation of 2 Legged OAuth using DNOA that would be helpful. If not, any ideas on how to implement would work too. Any help would be much appreciated. 回答1: I wasn't able to get DNOA to work with 2-legged OAuth so I ended up making my own consumer using http:/

2-legged OAuth implementation in C#

阅读更多关于 2-legged OAuth implementation in C#

问题 I'm trying to implement a two-legged OAuth authentication, so I can get to create a User on a website. I managed to craft this ruby code that performs that task, but I need to convert it to C#. I'm getting a 401 error when making the last POST in C#, but the code is practically the same. I'm getting crazy here. Can someone jump in and help me know what's wrong with my code? Ruby consumer = OAuth::Consumer.new(KEY, SECRET, :http_method => :post) # response = consumer.request(:get, "#{SITE}

Does google Drive api support 2 legged oauth?

阅读更多关于 Does google Drive api support 2 legged oauth?

问题 Now, we have an application with Google Docs Api and 2 legged oauth. However,we want to migrate to Google Drive Api which uses Oauth 2.0. Can we use 2 legged oauth with Google Drive Api? Is there any example? 回答1: You should use Service Accounts: https://developers.google.com/accounts/docs/OAuth2ServiceAccount 回答2: I just started looking into this and if I have any luck I will provide more info. However, if you are using 2 legged oauth so you can work with google apps domain-wide then there

Python GAE app using 2-legged OAuth and 3-legged OAuth at same time

阅读更多关于 Python GAE app using 2-legged OAuth and 3-legged OAuth at same time

问题 I'm coding a Python - Google App Engine application. There are 2 important things this app must do: Write in user's calendar. Write in user's profile (working with users in a Google Apps domain) First operation is easy. If I understood OAuth, this is the classical 3-legged scenario. The scenario for which OAuth was originally developed. The logged user provides credentials to the client (my app) to access the user's data (calendar) on his/her behalf. So, this can be done just with the logged

2-legged OAuth implementation in C#

阅读更多关于 2-legged OAuth implementation in C#

I'm trying to implement a two-legged OAuth authentication, so I can get to create a User on a website. I managed to craft this ruby code that performs that task, but I need to convert it to C#. I'm getting a 401 error when making the last POST in C#, but the code is practically the same. I'm getting crazy here. Can someone jump in and help me know what's wrong with my code? Ruby consumer = OAuth::Consumer.new(KEY, SECRET, :http_method => :post) # response = consumer.request(:get, "#{SITE}/oauth/request_token.json") # request_token_hash = JSON.parse(response.body) # puts request_token_hash

Python GAE app using 2-legged OAuth and 3-legged OAuth at same time

阅读更多关于 Python GAE app using 2-legged OAuth and 3-legged OAuth at same time

I'm coding a Python - Google App Engine application. There are 2 important things this app must do: Write in user's calendar. Write in user's profile (working with users in a Google Apps domain) First operation is easy. If I understood OAuth, this is the classical 3-legged scenario. The scenario for which OAuth was originally developed. The logged user provides credentials to the client (my app) to access the user's data (calendar) on his/her behalf. So, this can be done just with the logged user's credentials. Second operation is not so easy. It can't be done with just the logged user's