Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facing problem when hosting web application on IIS #16

Open
b42sonu opened this issue Dec 13, 2016 · 1 comment
Open

Facing problem when hosting web application on IIS #16

b42sonu opened this issue Dec 13, 2016 · 1 comment

Comments

@b42sonu
Copy link

b42sonu commented Dec 13, 2016

Hi,

I am working on C# MVC web application . In this application I am integrating google drive and using Google.Apis (version- 1.19.0.0). For this implementation I have taken the reference from your sample code and have implemented successfully in my application. During testing I have found that it is working fine when I run directly this from visual studio but when I deployed this on IIS (even local IIS) it is not working. After investigation I have found that it is giving problem in authentication and not trigger the authenticate screen with Gmail account. Mainly giving me on this below line :

UserCredential credential = GoogleWebAuthorizationBroker.AuthorizeAsync(new ClientSecrets {ClientId = clientId, ClientSecret = clientSecret} , scopes , userName , CancellationToken.None
, new FileDataStore(folder,true)).Result;

Nothing has happened after this line (no error) . Kindly help me on this . How I can solve this problem? Is there any setting in IIS that I need to set for this ?

Some trouble shooting I already done like :

  1. Given permission to folder (that store the outh response ). Like asp.net users .
  2. Tried with both folder default roaming folder and custom folder (for store the outh response)

Let me know if you want more information from my side.

Best regards,
Sunil Sharma

@LindaLawton
Copy link
Owner

I cant help to much I am not all that experienced with web applications. I can tell you that the problem is that IIS probably doesn't have permissions to write to what ever directory you are trying to save the credentials in. If memory services this has something to do with the application pool that IIS is running on but i cant remember more then that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants