OSL Social Login Pro – Client-to-Backend Verification


An end-to-end Unity sign-in workflow that connects multi-provider client login to your own .NET 8 verification backend starter.


by OngsooLabs


Price History +

OSL Social Login Pro is for Unity teams that want one documented path from provider sign-in in the game client to verification on their own backend. It combines the SocialLogin client integration layer with TokenVerification's Unity request manager and .NET 8 server starter, so the credential handoff does not need to be designed from scratch.


Why / Key Benefits

- Connect both halves of sign-in: Acquire a provider credential through the unified client API and send it to the matching backend endpoint.

- Reduce provider integration work: Configure Google, Facebook, Apple, Steam, and Discord adapters through the Social Login setup workflow.

- Keep verification under your control: Start from a .NET 8 backend project that implements the five provider-specific verification paths.

- Preserve modular boundaries: SocialLogin and TokenVerification remain separate modules joined by credential strings and HTTP request contracts.

- Configure providers independently: Conditional provider code and build processors let the project enable only the integrations it uses.


Typical Workflow

1. Configure the selected provider in `Tools > OSL > Social Login Setup`.

2. Run the provider sign-in flow and receive its credential in Unity.

3. Send the credential through `TokenVerifyManager` to your .NET 8 service.

4. Let the provider-specific endpoint validate it, then connect the verified identity to your own account/session system.


Requirements

- Minimum Unity Version: Unity 2021.3 LTS

- Tested Unity Versions: Unity 2021.3.45f2 and Unity 6000.3.12f1 (package-isolation import and compile)

- Backend runtime: .NET 8 SDK/runtime

- Provider prerequisites: Credentials, dashboard configuration, and any vendor SDK/runtime required by each enabled client provider

- Included verification paths: Google, Facebook, Apple, Steam, and Discord


Limitations / Scope

- This bundle supplies an integration workflow and backend starter; it does not prove a production deployment or successful login with your provider accounts.

- Hosting, HTTPS, secret storage, abuse controls, account linking, session issuance, and provider approval remain project responsibilities.

- Steam and browser-loopback platform limits are the same as the included SocialLogin module.


Documentation & Support

https://ongsoolabs.github.io/