We are in the process of setting up an API that allows real-time location data to be pulled in GeoEvent and then published to a Feature Layer for a map. The overall workflow is fine, however we have run in to issues with the established API authentication method. The third-party software requires token authentication for the API, and this token refreshes every hour. There are no other authentication options. We are trying to determine if there is an existing method to grab this token and automatically pass it on to the input pulling the location data.
We have searched for documentation demonstrating how to do this using existing GeoEvent tools (e.g., building a custom connector, downloading a custom connector from ESRI's GitHub), but have not been able to find anything that is recent or fits our use-case. The only thing we found is this (https://github.com/Esri/http-inbound-auth-token-for-geoevent) but it is from 10.4 and our environment management team is skeptical as to whether it is compatible/will work as needed. We are currently using 10.9.1, but plan to upgrade when 11.1 is released.
Does anyone know if this is possible or if this is potentially in the works for the update? More and more secure APIs are relying on a refreshable token instead of a user/pass, and up until this point we have been able to develop a work around outside of GeoEvent.
Also, any similar posts or documentation would be helpful! We aren't opposed to developing our own, truly custom input connector, but would prefer to use established methods if possible.
