SSO - defaultSSO config vs sso.register
I ran into an issue with SAML2 SSO, but atm i am unsure if my usage of better-auth and @better-auth/sso is correct for my use case.
The use case us as follows: There will be one and only one provider logging into my application.
I would like to restrict better-auth to only handle this one provider.
Is this better done with:
1. sso.register(org) + config value providersLimit: 1 -> Creates a DB entity and no longer allows new providers to be created
2. defaultSSO + config value providersLimit: 0 -> Does not allow SSO providers to be registered, but always uses the static values provided when bootstrapping app, through the config.
The use case us as follows: There will be one and only one provider logging into my application.
I would like to restrict better-auth to only handle this one provider.
Is this better done with:
1. sso.register(org) + config value providersLimit: 1 -> Creates a DB entity and no longer allows new providers to be created
2. defaultSSO + config value providersLimit: 0 -> Does not allow SSO providers to be registered, but always uses the static values provided when bootstrapping app, through the config.
