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

Bug: Extension is breaking REST API #25

Closed
logeecom opened this issue Aug 25, 2017 · 3 comments · Fixed by #30
Closed

Bug: Extension is breaking REST API #25

logeecom opened this issue Aug 25, 2017 · 3 comments · Fixed by #30

Comments

@logeecom
Copy link

logeecom commented Aug 25, 2017

When extension is installed and active, REST API is not working properly. Authentication passes as expected but issuing any GET request breaks. For example, calling GET on /api/rest/products and Magento is giving this response:

{
	"messages" : {
		"error" : [
			{
				"code" : 401,
				"message" : "oauth_problem=internal_error&message=SQLSTATE[42S22]: Column not found: 1054 Unknown column 'mg82_oauth_nonce.nonce_id' in 'where clause', query was: SELECT `mg82_oauth_nonce`.* FROM `mg82_oauth_nonce` WHERE (`mg82_oauth_nonce`.`nonce_id`='0')"
			}
		]
	}
}

Here is a request:
image

When extension is disabled, everything works as expected.

@krombox
Copy link

krombox commented Oct 2, 2017

Confirmed. After debugging found that disabling this extension back REST API to live

@roman204
Copy link
Member

this is cause the extension tries to log history of Mage_Oauth_Model_Nonce

@Schrank
Copy link
Member

Schrank commented Jan 15, 2018

Thanks @roman204 for debugging! If someone provides a PR, we can merge it :-)

Solution should be easy: Just blacklist Mage_Oauth_Model_Nonce in config.xml

dh1984 added a commit to dh1984/firegento-adminmonitoring that referenced this issue Jun 12, 2018
This was referenced Jun 12, 2018
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

Successfully merging a pull request may close this issue.

4 participants