Jump to content

Recommended Posts

Posted

Hi,

The php build we upgrade to: 8.1.13

Mysql: 8.0.33

As now our API login throw out error:

Quote

Our OAUTH sign in is not working. Existing connections/authorizations i think are okay but any attempt to authorize a user is returning Invalid_Grant (which is just the generic error) with a description of "400" which I would think would imply some sort of parameter error (like something changed we don't know about).

Thanks.

Posted

After upgrade PHP, you will want to run the compatibility checker to ensure that there are not any missing modules. If something was working and the software was not updated, it sounds like you are missing something:

 

Posted

You will want to double check the request which you are sending to the OAuth endpoint and ensure that all endpoints are authorized correctly. Additionally, you will want to enable logging for OAuth endpoint so you can see what is happening. Currently, there are no errors as logging is disabled on your endpoints.

Posted
41 minutes ago, abobader said:

We tried everything, only option we have now to roll back to 4.7.14.

You would want to do as mentioned above, without the logging, we won't know what is happening.

Posted

@Jim M But it was working, can the case will be from the forum generic OAuth validation that is built into IPB, it work for 20 minutes then stopped.

As you see here:

Quote

[Thu Aug 15 14:55:57.621751 2024] [php:notice] [pid 29281:tid [client 173.230.139.54:39616] [realclient 31.221.164.22] Successfully created user 1488928/

The REST API is functioning fine.

What is failing is the generic OAuth validation that is built into IPB - but it worked for 20 minutes

Really, we run out of all idea.

Posted

That would be the PHP log. Not the OAuth log in our software. This is in ACP -> System -> API -> OAuth -> edit the OAuth key, expand the endpoint you're using and check Log.

If it is working then stops, sounds like this is something with the server or the IP address in question is getting banned. 

Posted

 @Jim M One question:

Is the OAuth grant type of "password" has been deprecated in this version (4.7.18)?

Thanks.

Here the code:

Quote

$curl = curl_init( $oathUrl ); curl_setopt_array( $curl, array( CURLOPT_RETURNTRANSFER => TRUE, CURLOPT_HTTPAUTH => CURLAUTH_BASIC, CURLOPT_HEADER => "Content-Type:application/x-www-form-urlencoded", CURLOPT_POST => TRUE, CURLOPT_POSTFIELDS => "grant_type=password&username=$cleanEmail&password=$password&client_id=$oathId&client_secret=$oathSecret&scope=profile" ) );

Thanks in advance for all the help Jim.

Posted

Sorry, we would not be able to assist with custom code. 

33 minutes ago, Jim M said:

OAuth log in our software. This is in ACP -> System -> API -> OAuth -> edit the OAuth key, expand the endpoint you're using and check Log.

If it is working then stops, sounds like this is something with the server or the IP address in question is getting banned. 

These would be the items you need to look at

Posted

No problem Jim, I know that, we just hope we did not make any error, strange, it was working well till this update.

@Jim M Sorry for many questions, last one:

grant_type=password 

still supported?

Thanks

Posted

These would be the grant types which are supported:

Could contain: Computer Hardware, Electronics, Hardware, Text, Chart, Plot

Resource Owner Password Credentials is supported.

Posted

Hi,

Now we faced slow when someone switching to fluid view, it took like 20-25 to switch to it, normal (table/grid) do not have that problem, any head up info regarding that.

Thanks

Posted
3 hours ago, abobader said:

Hi,

Now we faced slow when someone switching to fluid view, it took like 20-25 to switch to it, normal (table/grid) do not have that problem, any head up info regarding that.

Thanks

If its taking that long, you need to look at your servers setup

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...