Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Feathers-authentication assumptions #220
I am trying to leverage the
This means I don't want to create a user. Right now leveraging the flow through feathers-authentication causes a user to be created. Additionally, I need to grab other things from the payload from Slack but I'm not understanding how to do that. It's in the response but need to do further things with creating another service (i.e Integration). Is there a way to do a callback of some sort?
Is it in feathers-authentication's vision to support bypassing creating a user, or should I drop down to express and leverage vanilla passport?
@dfischer if you need stuff from the Slack response payload, why not turn the users service into a memory store? Let feathers-authentication save the payload to memory, grab the data you want, then clear the user record from the memory store, so it won't be sitting around.