Another question regarding the authentication: the...
# getting-started
c
Another question regarding the authentication: the API i'm using requires a token, which is then used with different IDs to generate a JWT token. The last token enables me to get even more specific data related to the IDs. Should I create different Auths? Could you guide me a bit please?
t
Are you building a tap with the SDK?
c
Yes!
I've been using the SDK and I've so far only implemented the differents Streams (name, path, pk, replicationkey and schema_filepath). I've been browsing several other taps to see if a relatable situation existed. But could not find quite the thing.
t
Cool - I’ll loop in @aaronsteers since he’s the expert on all things SDK. Also, I don’t know if this works with your schedule but we have office hours at 1600 UTC (11 AM central) and that’d be a good time to ask the question live too.
c
Thanks! I'll see how I can make it work, time-wise
t
We’re starting office hours if you’re able to join 🙂 https://gitlab.zoom.us/j/96641645026
a
Hi, @charley_guillaume - You can certainly create different authenticators and send each to a different stream - or more likely, each to a different stream base class.
So, if you declare AuthenticatorA and AuthenticatorB, you might create two base classes for your streams as well. There are probably other approaches as well, for instance you could just override the behavior in a single Stream class if only that one stream needs to behave differently.
This is a slightly different use case, but we have a example in our tap-gitlab sample which declares one base class for GraphQL-typed streams and one for REST-typed streams. The tap class itself can use these intermixed and doesn’t need to know the details, since each stream manages its own connection process. singer_sdk/samples/sample_tap_gitlab · main · meltano / Singer SDK · GitLab
c
@aaronsteers thanks so much for your feedback! I'll try that direction then! :)