Title: Problem with “code” url request
Last modified: November 16, 2022

---

# Problem with “code” url request

 *  Resolved [Tii](https://wordpress.org/support/users/tii/)
 * (@tii)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/problem-with-code-url-request/)
 * in the file class-mo-oauth-widget.php on line 340, the if has isset($_REQUEST[‘
   code’]) as one of the condition to get into it.
    Unfortunatly, this is causing
   problem with one of my other custom made plugin who is sending out links with
   a “code” request in it. Would it be possible to review this condition and maybe
   add one more condition to it in order to avoid breaking all links that would 
   have a “code” request in it ?

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [ameyatammewar](https://wordpress.org/support/users/ameyatammewar/)
 * (@ameyatammewar)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/problem-with-code-url-request/#post-16246615)
 * Hi,
 * Thank you for reaching out to us.
 * As per the standard SSO protocols like OAuth 2.0 and OpenID connect 1.0, in the
   authorization code grant, the code parameter was sent as a response from the 
   Identity provider in the $_REQUEST, you can check the details in [the RFC specifications](https://www.rfc-editor.org/rfc/rfc6749#page-26).
   That’s why we cannot modify the condition as we are receiving the response from
   IDP and our plugin has to catch that response for further processing. But we 
   can add a check to handle the request coming from your custom code.
 * You can share your request format, the parameter required along with code, so
   we can add a check in our plugin for that. You can send us a query from the support
   form inside the plugin. We will be happy to help you.
 * Thanks,
 *  Thread Starter [Tii](https://wordpress.org/support/users/tii/)
 * (@tii)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/problem-with-code-url-request/#post-16719051)
 * I have no problem with you testing the response, the problem is that there is
   just a simple condition that is isset($_REQUEST[‘code’]) with non of your context
   or route it should be tested on, meaning that anybody who would use a ‘code’ 
   request parameter would crash his website!
 * The should be a condition like
 * (isset($_REQUEST[‘code’]) && inMiniOrangeWidgetContext())
 * in order to avoid this

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Problem with “code” url request’ is closed to new replies.

 * ![](https://ps.w.org/miniorange-login-with-eve-online-google-facebook/assets/
   icon-128x128.png?rev=3419722)
 * [OAuth Single Sign On - SSO (OAuth Client)](https://wordpress.org/plugins/miniorange-login-with-eve-online-google-facebook/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/miniorange-login-with-eve-online-google-facebook/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/miniorange-login-with-eve-online-google-facebook/)
 * [Active Topics](https://wordpress.org/support/plugin/miniorange-login-with-eve-online-google-facebook/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/miniorange-login-with-eve-online-google-facebook/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/miniorange-login-with-eve-online-google-facebook/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Tii](https://wordpress.org/support/users/tii/)
 * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/problem-with-code-url-request/#post-16719051)
 * Status: resolved