Custom IdP with BetterAuth
Hi guys,
We are exploring using BetterAuth for our new app and we have a few constraints that I am not sure how to address with BetterAuth based on my research.
We would like to use BetterAuth as authorization server and to implement OAuth based log in using OIDC plugin, but to have custom identity provider. Also, we would like to keep BetterAuth sessions and JWT functionality. Use case is the following:
* we want to use BetterAuth in two different services/modules: Auth and MFA
* we have few different user types: admins, business users and normal users
* each of those user credentials are stored in different microservices: admin service, business service and user service
* we would like to look for credentials in each individual service during log in
Also, we have a separate MFA service where we would like to utilize BetterAuth capabilities for 2FA and its existing integrations. If we introduce second instance of BetterAuth in MFA service, I would not like core tables to be recreated in different schemas.
Questions are:
* is there are way to minimize Core schema creation from BetterAuth?
* will writing custom DB adapter or some plugin help and override behavior?
* not sure what are absolute must have tables for BetterAuth to work?
We are exploring using BetterAuth for our new app and we have a few constraints that I am not sure how to address with BetterAuth based on my research.
We would like to use BetterAuth as authorization server and to implement OAuth based log in using OIDC plugin, but to have custom identity provider. Also, we would like to keep BetterAuth sessions and JWT functionality. Use case is the following:
* we want to use BetterAuth in two different services/modules: Auth and MFA
* we have few different user types: admins, business users and normal users
* each of those user credentials are stored in different microservices: admin service, business service and user service
* we would like to look for credentials in each individual service during log in
Also, we have a separate MFA service where we would like to utilize BetterAuth capabilities for 2FA and its existing integrations. If we introduce second instance of BetterAuth in MFA service, I would not like core tables to be recreated in different schemas.
Questions are:
* is there are way to minimize Core schema creation from BetterAuth?
* will writing custom DB adapter or some plugin help and override behavior?
* not sure what are absolute must have tables for BetterAuth to work?
