Is your feature request related to a problem? Maybe it would be better as discussion? Please describe.
Currently, if ENABLE_SENDING_INVITES=true is used, SplitPro generates its own local magic links and bypasses OIDC entirely. This breaks centralized identity management and creates local-only shadow accounts that exist outside of my SSO provider.
Describe the solution you'd like
The simplest and most helpful solution would be the ability to configure a custom URL for the invite system via an environment variable (e.g., CUSTOM_INVITE_URL=https://auth.mydomain.com/enroll). When a user taps "Invite" or shares a link from the app, it would output this custom URL instead of the default local routing.
Alternatively, a more robust solution would be a native OIDC onboarding integration, where the app recognizes it is in an OIDC-only lockdown state and defers all invite generation/links to the configured OIDC provider's enrollment flow. But that is probably a lot more work. A custom variable would honestly do the trick a lot easier.
Describe alternatives you've considered
Currently, the only alternative is to set ENABLE_SENDING_INVITES=false and completely ignore the invite functionality in the SplitPro UI. I have to manually send users my SSO enrollment link via text or email outside of the app, wait for them to register, approve them, and then have them log into SplitPro. While this works securely, it creates a disconnected UX for friends and family who expect the app's native invite buttons to function.
App version
v2.1.0 (Using the ossapps/splitpro:latest Docker image).
Is your feature request related to a problem? Maybe it would be better as discussion? Please describe.
Currently, if
ENABLE_SENDING_INVITES=trueis used, SplitPro generates its own local magic links and bypasses OIDC entirely. This breaks centralized identity management and creates local-only shadow accounts that exist outside of my SSO provider.Describe the solution you'd like
The simplest and most helpful solution would be the ability to configure a custom URL for the invite system via an environment variable (e.g.,
CUSTOM_INVITE_URL=https://auth.mydomain.com/enroll). When a user taps "Invite" or shares a link from the app, it would output this custom URL instead of the default local routing.Alternatively, a more robust solution would be a native OIDC onboarding integration, where the app recognizes it is in an OIDC-only lockdown state and defers all invite generation/links to the configured OIDC provider's enrollment flow. But that is probably a lot more work. A custom variable would honestly do the trick a lot easier.
Describe alternatives you've considered
Currently, the only alternative is to set
ENABLE_SENDING_INVITES=falseand completely ignore the invite functionality in the SplitPro UI. I have to manually send users my SSO enrollment link via text or email outside of the app, wait for them to register, approve them, and then have them log into SplitPro. While this works securely, it creates a disconnected UX for friends and family who expect the app's native invite buttons to function.App version
v2.1.0 (Using the
ossapps/splitpro:latestDocker image).