Is Passport useful if I already have an API with OAuth2 authentication?
My current project requires me to use the Canvas API. https://canvas.instructure.com/doc/api/ This API has OAuth2 authentication, I have the means to create clients on it, and can make redirects using it.
Depending on if some person is logged in based on Canvas information, they're permitted onto the page they want, or redirected elsewhere.
Since I use Laravel, some have recommended Passport to me, but since Passport seems to be all about setting up an OAuth2 server, is it redundant if I already have one? Or is there some other end to which I might need it?
Not really. I mean, I like Passport a lot. When dealing with Blade or Vue, basically anything Laravel / self-digesting, it really handles all of the lifting for you... and it gives some power to create all the tokens needed when building out a developer API.
If you already have Oauth2 implemented... I can't see any benefit to walking that back and using Passport, except to argue that it is done "The Laravel Way", which you might decide is nice.
It is helpful, thank you very much for replying. Documentation on this combination of software is sparse, so when some recommend it while I'm trying to use another element, I'm glad for clarity when I can find it.
