Hi @henrikstagnell, have you already had a look at this article on Web Connections and FME? There's a section that describes OAuth 2.0 connections that might be helpful to configuring your own connection
Hi @henrikstagnell as @jovitaatsafe mentioned. The article is a good starting point.
For most cases, leaving the default Redirect URI values works for FME Desktop ("urn:ietf:wg:oauth:2.0:oob").
Or else you can try using 'http://localhost' as well, if HTTPS is required, please ensure that the certificate is present on the FME Desktop machine.
Have you configured the app correctly on the Mapillary API?
I would advise adding all the variations of redirect URI in the application(Mapillary.com).
FYI - The OAuth2.0 template is configured to have a Refresh token workflow.
Hi @henrikstagnell
I have done a quick test, I am not familiar with the API myself but I was able to try it using the instructions.
After creating the OAuth2.0 services following the developer API documentation, I was able to set up a web service and able to generate a token see a short demo here
Here is the configuration and URL that I used for this test.
I am having an error when clicking at authorize.
Can anyone help me out, where I am making a mistake?? I am trying to fetch Traffic Signal features...!
Thanks.
I am having an error when clicking at authorize.
Can anyone help me out, where I am making a mistake?? I am trying to fetch Traffic Signal features...!
Thanks.
I managed to make this work by adding Authorization under HTTP Header for Retrieve Token Parameters:
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.