Is there a recommended way to handle authenticatio...
# singer-tap-development
a
Is there a recommended way to handle authentication for targets? All the
singer-sdk
authenticators seem really useful, but are pretty tightly coupled to Streams, which are a tap concept rather than a target concept. I realize this is likely due to the ecosystem as a whole using more of a pull model than a push model, but targets inherently don't have any different of a requirement as far as authentication goes. Is the best way to just manually handle things? For instance, when working with OAuth, do error handling and the token refreshes yourself?
e
Yeah, we don't have a generic REST target class but if it existed I think it would need to accept any auth callable. I would also like to make the sdk's built-in authenticators more generic (and also #2040), but that'd require going through a deprecation process 😬.
v
I do it manually today 🤷
Don't forget about adding a timeout to your request, made that one (infinite running requests is no fun! 😄 )