Integration of Custom Third-Party Authentication in Wasp
I am currently developing an application using Wasp and aim to integrate a custom third-party authentication system. This system requires sending a combination of login and password to a specific API endpoint and receiving a DTO containing a user ID in response. My objective is to utilize this user ID to either log in existing users or create new accounts within my Wasp application, effectively replacing the default authentication methods.
Could you provide guidance on the best practices for implementing such a custom authentication flow in Wasp? Specifically, I am interested in:
The recommended approach to send user credentials to the external API securely and handle the response appropriately.
How to manage user sessions and state within Wasp when bypassing the built-in authentication mechanisms.
Any potential challenges or considerations to be aware of when integrating a custom authentication method that deviates from the standard social authentication providers supported by Wasp.
I appreciate your assistance and any documentation or examples you can provide to facilitate this integration.
Best regards,
Could you provide guidance on the best practices for implementing such a custom authentication flow in Wasp? Specifically, I am interested in:
The recommended approach to send user credentials to the external API securely and handle the response appropriately.
How to manage user sessions and state within Wasp when bypassing the built-in authentication mechanisms.
Any potential challenges or considerations to be aware of when integrating a custom authentication method that deviates from the standard social authentication providers supported by Wasp.
I appreciate your assistance and any documentation or examples you can provide to facilitate this integration.
Best regards,
