A user asks: can APG vNext be integrated with an existing ASP.NET membership database so that users do not need to register twice — once for the main site and once for the forum?
The Answer
Yes — APG vNext supports integration with existing ASP.NET membership providers. You can configure the forum to use your existing membership database by pointing APG vNext at your existing SQL membership tables.
How to Integrate with an Existing Membership Database
- Open Admin Panel → Configuration → Membership Provider.
- Set the connection string to point to your existing membership database.
- Set the ApplicationName in your
web.configto match the application name used by your existing membership tables. - APG vNext will then authenticate users against the shared database, enabling single sign-on (SSO) across your applications.
Custom Membership Provider Support
APG vNext also supports custom membership providers. If your existing application uses a non-standard membership implementation, you can create a class that inherits from MembershipProvider and configure APG vNext to use it via the standard ASP.NET provider model in web.config.
Related Resources
Integrating APG vNext with an Existing Membership Database
Organizations that already maintain a user database for another application commonly ask whether APG vNext can be integrated with that existing membership system. The answer is yes, through multiple integration approaches ranging from simple database-level linking to full ASP.NET Membership Provider customization. The right approach depends on how different your existing user schema is from the standard APG vNext schema, how you want users to authenticate, and whether you need single sign-on across both systems.
Shared SQL Server Database Approach
The simplest integration is configuring APG vNext and your existing application to share the same SQL Server database while maintaining separate user tables linked by a common identifier such as email address or a shared user ID. In this scenario, users register once and a cross-application synchronization trigger creates records in both applications' user tables. Login happens separately in each application, but the user's account exists in both without requiring separate registration.
ASP.NET Membership Provider Integration
For true single sign-on, both APG vNext and your existing application must share the same ASP.NET Membership Provider and machine key configuration. Configure the same applicationName value in both applications' membership provider configuration sections. Set identical machineKey values in both web.config files. Configure the Forms Authentication cookie with a shared domain scope so a login in one application is recognized by the other without requiring the user to log in again for each application separately.
Custom Membership Provider Bridge
If your existing user schema is significantly different from the standard ASP.NET Membership schema, implement a custom Membership Provider class in APG vNext that delegates authentication calls to your existing user authentication system. The minimum methods to implement are ValidateUser, GetUser, GetUserNameByEmail, and CreateUser. This approach provides maximum flexibility but requires custom .NET development work to implement and maintain correctly across APG vNext upgrades.
Testing the Integration Thoroughly
After configuring any database or membership integration, test all critical user journeys: registration in both systems, login from both systems after registering in the other, password reset workflows, email notification delivery, and account lockout behavior. Integration bugs often surface only at the boundaries between systems and during edge cases like concurrent logins or password changes, so comprehensive testing is essential before opening the integrated system to real users.
APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes.Looking for more help? Browse the support forum or check the Knowledge Base.