Weke ID
Keep identity handoff scoped to the right audience every time
Weke ID is the shared sign-in boundary for Weke products, handling audience-aware login, registration, and secure returns without exposing arbitrary redirect paths.
Use fixed return targets instead of open redirects
Send people back into the correct Weke workspace
Weke ID
Weke ID Features
Review the workflows, controls, and day-to-day operating detail behind Weke ID for audience-aware sign-in, secure returns, identity handoff, and product access scope.
Resolve the right audience before sign-in begins
Weke ID keeps login and registration scoped to the requested product so users do not land in an unrelated workspace after authentication.
Use fixed return targets instead of open redirects
Every product comes back to an allowlisted callback path, preserving the real /app handoff contract without accepting arbitrary visitor-supplied URLs.
Send people back into the correct Weke workspace
Identity flow ends at the intended product entry so operators and customers land in the place that matches their audience and task.
Weke ID
Weke ID Workflow
Follow the three operating steps that keep identity, sign-in boundaries, audience scope, and secure returns moving.
Resolve the host, audience, and return target
The incoming request is matched to the correct product audience and fixed callback destination before login begins.
Run sign-in or registration inside the identity boundary
Weke ID handles the credential step while the product keeps its own scope, branding, and callback rules.
Return only to the allowlisted workspace
After identity is complete, the user lands back on the intended Weke /app route with no cross-product leakage.
Keep identity handoff scoped to the right audience every time
Weke ID handles login and registration for Weke ID and returns only to https://id.wekedev.com/app.