OSL Social Login Pro
OSL Social Login Pro connects multi-provider sign-in in Unity to verification on your own .NET 10 backend starter. It bundles OSL Social Login, OSL Token Verification, and OSL Core so the credential handoff does not need to be designed from scratch.
Overview
Use Social Login Pro when a project needs both the Unity-side provider adapters and a server-side verification starting point. The included modules remain separate assemblies, while the export packages the client integration and five provider-specific backend paths together.
Social Login 1.2.0 and Token Verification 2.0.0 Included
Social Login Pro 2.0.0 includes Social Login 1.2.0 and Token Verification
2.0.0. The existing basic
login and SocialLoginResult.Token handoff remain available; typed credentials
are optional advanced controls. Google Windows handles PKCE S256 and state
inside the package without a Unity client secret, and the default timeout,
cancellation, callback cleanup, and duplicate-request protection do not add
setup fields for basic use. The bundled backend now requires .NET 10 and uses
production-safe CORS, Swagger, rate-limit, request-size, timeout, health,
correlation, error, and logging defaults. Existing .NET 8 deployments must stay
on Social Login Pro 1.3.0 or migrate before upgrading.
Included Workflow
- Configure the required provider in Tools > OSL > Social Login Setup.
- Extract
Assets/OSL/TokenVerification/Server_Dotnet_Source.zipfrom the bundled TokenVerification folder. - Configure and run the extracted .NET 10 backend project.
- Send the token obtained by Social Login to
TokenVerifyManagerfor server-side verification.
For the basic client flow, setup asks only for the active target's required identifier. Provider-specific PKCE, state, callback, and default timeout handling stay inside Social Login rather than becoming extra setup fields.
Requirements
- Unity 2021.3 LTS minimum
- Unity 2021.3.45f2 and 6000.3.12f1 tested for package-isolation import and compile
- Latest servicing release of the .NET 10 SDK for the included backend template
- Provider SDKs and credentials required by the providers selected for the project
This package supplies an end-to-end integration workflow, not proof of a production deployment or successful login with your provider accounts. The starter provides production-safe defaults, but project-specific HTTPS termination, secrets, monitoring, account linking, abuse policy, and session issuance remain project responsibilities.