Field Kit Login Issue

[Geeksteader]

Hello all! I recently installed farmOS on my own web hosting, so I’m new to it but it’s going well so far. However, attempting to log in to the field kit at farmos.app with my domain and farmOS user credentials I get a 500 error and it won’t log in. Any help would be appreciated!

[mstenta]

Hi @Geeksteader! Welcome to the farmOS forum!

I get a 500 error and it won’t log in

500 errors are usually accompanied by some kind of PHP error in the server logs. You might find a useful clue there.

the field kit at farmos.app

Please note that Field Kit is in “alpha” status. This might give a better sense of where things stand:

Field Kit Status Update

I finally had a chance to triage some of the issues that have accrued since last year and then pick up the thread of what needs to be done going forward. The image/file stuff is still sooooo close to being done but just figuring out a few lingering issues, then it’s just a matter of giving the Observations module a basic UI for adding images to observation logs. That should complete the alpha.9 release. After that, the remaining tasks for the beta release are mostly housekeeping, with the 2 most…

[Geeksteader]

Thanks! Based on the server logs I was able to resolve that error (I needed to configure and generate the OAuth keys), but now I have a 400 error, with the log saying user credentials are incorrect, even though it’s the same credentials I sign into farmOS with.

I also tried using the JavaScript API with the default API consumer and got the same error with the authorize function, so I must not have something configured right.

---

As far as the alpha status, I guess I was mostly intending to sign in to see what it looked like and how stable it is, not to use regularly necessarily, but maybe I’d be better holding off on that in case there’s a risk of data corruption.
Are there any major known issues it has right now? Or mostly just unimplemented or partially implemented features?

I’m not proficient in JS or backend web technologies (though I can generally learn quickly), but I may consider contributing to farmOS or the Field Kit in the future if I can find the time.

[mstenta]

@Geeksteader

now I have a 400 error, with the log saying user credentials are incorrect

Hmm I wonder if this is related/helpful at all?

Invalid_scope when trying to login to Field Kit

I’m trying to use Field Kit (via https://farmos.app) to log in to my farmOS 3.0.0-beta3 instance. After clicking “Submit credentials”, I get a “Request failed with status code 400” error. Using the Chrome devconsole, I can see that it’s doing a POST to https://my.farmos.instance/oauth/token and getting this as a response: { "error": "invalid_scope", "error_description": "The requested scope is invalid, unknown, or malformed", "hint": "Check the `farm_manager` scope", "message":…

That fix was merged last year, though, so probably not exactly the same issue. But maybe related.

Just to be sure: did you enable the farm_fieldkit module (for Field Kit connection) and the farm_api_default_consumer module (for raw API use)? These both depend on the simple_oauth_password_grant module, which adds the ability to use password grants.

@Geeksteader

Are there any major known issues it has right now? Or mostly just unimplemented or partially implemented features?

See the link I posted above to @jgaehring’s update for more details on where things stand.