Answers.Body: <p>You can set <code>usePathInfo = true</code> in your Craft general settings to force Craft to use PATH_INFO to generate URLs.</p>
  
  <p><a href="https://craftcms.com/docs/config-settings#usePathInfo" rel="nofollow">https://craftcms.com/docs/config-settings#usePathInfo</a></p>
  
  <p>Dukt OAuth should now show you a redirect URI without a query string (Facebook doesn’t like slashes in the query string and automatically encodes them) and you should be able to make the URIs match exactly.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T13:55:23.483Z
Answers.LastActivityDate: 2016-05-13T13:55:23.483Z
Answers.UserDisplayName: carlcs
Body: <p>I am getting an error with oauth (1.0.79) when using Facebook:</p>
  
  <blockquote>
    <p>Required option not passed: access_token Array (
    [{"error":{"message":"Error_validating_verification_code__Please_make_sure_your_redirect_uri_is_identical_to_the_one_you_used_in_the_OAuth_dialog_request","type":"OAuthException","code":100,"fbtrace_id":"A2ThFvRVsAZ"}}]
    => )</p>
  </blockquote>
  
  <p>Facebook is changing the url entered and replacing the /'s in the p=actions/oauth/connect part of the redirect URI with ASCII characters %2F p=actions%2Foauth%2Fconnect which I assume is then not matching the 2 uri's causing the above error.</p>
  
  <p>Is this the issue? Is there a workaround? Or is this a tweak that needs to be made to oauth?</p>
  
  <p>Cheers</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-08T01:15:00.100Z
Comments.Text: You are correct that it is an encoding error. I have reported it to Dukt here: https://github.com/dukt/craft-oauth/issues/18. In the mean time, you can modify oauth/providers/Facebook.php and just hardcode the redirectUrl with the last two forward-slashes replaced with %2F.
Comments.UserDisplayName: Eli Van Zoeren
Tags: <plugin-duktoauth>
Title: Oauth Facebook Issue with redirect URI
ThreadText: # Oauth Facebook Issue with redirect URI
  
  (Asked by: username_0 on 2016-02-03)
  
  I am getting an error with oauth (1.0.79) when using Facebook:
  
  > Required option not passed: access\_token Array (
  > [{"error":{"message":"Error\_validating\_verification\_code\_\_Please\_make\_sure\_your\_redirect\_uri\_is\_identical\_to\_the\_one\_you\_used\_in\_the\_OAuth\_dialog\_request","type":"OAuthException","code":100,"fbtrace\_id":"A2ThFvRVsAZ"}}]
  > => )
  
  Facebook is changing the url entered and replacing the /'s in the p=actions/oauth/connect part of the redirect URI with ASCII characters %2F p=actions%2Foauth%2Fconnect which I assume is then not matching the 2 uri's causing the above error.
  
  Is this the issue? Is there a workaround? Or is this a tweak that needs to be made to oauth?
  
  Cheers
  
  **Tags:** plugin-duktoauth
  
  > **Comments:**
  > **username_1**: You are correct that it is an encoding error. I have reported it to Dukt here: https://github.com/dukt/craft-oauth/issues/18. In the mean time, you can modify oauth/providers/Facebook.php and just hardcode the redirectUrl with the last two forward-slashes replaced with %2F.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2016-05-13. Score: 1
  
  You can set `usePathInfo = true` in your Craft general settings to force Craft to use PATH\_INFO to generate URLs.
  
  <https://craftcms.com/docs/config-settings#usePathInfo>
  
  Dukt OAuth should now show you a redirect URI without a query string (Facebook doesn’t like slashes in the query string and automatically encodes them) and you should be able to make the URIs match exactly.
  
  
  ---
  
  