You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I experienced an authorization error during the onboarding process, after creating the application. The application said, that there was a failure to process authorization.
I took a look into the developer console and saw, that there was an HTTP 400 on the request.
I then checked the payload and realized, that the redirect_uri is missing within the request.
After adding the missing information, the onboarding response was redirected to the application.
Since the former implementation of the agrirouter did only use a single field to provide a redirect URL, the addition of the deep URL could be misleading and adding the redirect URL can be easily forgotten - @oliverrahner, wdyt?
I think at least one redirect URL should be mandatory, since the request relies on the information and the onboarding process will fail otherwise.
agrirouter SDK
Java
Support Data
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Unfortunately, there are some edge cases that we know of which explicitly don't need a redirect URL. Example would be a Farming Software that is running locally on a Desktop. While you could use a redirect in those cases as well, there are implementations solely relying on entering a registration code.
What we could, and should, probably do though, is show some kind of a warning next to the Redirect URL setting if you didn't set any, to put the focus there.
And then also handle this case more gracefully during authorization.
Reclassified as future enhancement because of the statement above
oliverrahner
changed the title
[Bug] Missing redirect URI leads to problems during onboarding
[Enhancement] Missing redirect URI leads to problems during onboarding
Aug 26, 2024
Hey, we have just rolled out a small related improvement in the authorization process, one of two that Oliver mentions above. Now when user opens authorize page with wrong redirect URI, they would see error page right away, without showing Connect button.
This would look approximately like this (wording of error messages might change a bit though):
and in mobile resolutions:
Contact Details
No response
What happened?
I experienced an authorization error during the onboarding process, after creating the application. The application said, that there was a failure to process authorization.
I took a look into the developer console and saw, that there was an HTTP 400 on the request.
I then checked the payload and realized, that the
redirect_uri
is missing within the request.After adding the missing information, the onboarding response was redirected to the application.
Since the former implementation of the agrirouter did only use a single field to provide a redirect URL, the addition of the deep URL could be misleading and adding the redirect URL can be easily forgotten - @oliverrahner, wdyt?
I think at least one redirect URL should be mandatory, since the request relies on the information and the onboarding process will fail otherwise.
agrirouter SDK
Java
Support Data
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: