Continue with your MOS Workspace identity. Single Sign-On — no password required.
Your workspace administrator manages this identity. MOS ID only receives your verified email and profile.
Authenticating with MOS Workspace…
Establishing secure SSO session
Link your GitHub profile metadata directly
Receive real-time security alerts on Telegram
Scan this QR code with Google Authenticator or any TOTP app
Secret: —
Register a new authorised access context
Sign in to your MOS ID workspace
Start building with MOS Cloud
Enter the 6-digit verification code generated by your TOTP authenticator app.
This application will receive your email address:
Starter plan: 3 applications
Embed this snippet in your client application to receive the callback token and user details after SSO authorization.
Select an application context first...
Go from zero to a working “Sign in with MWS” button in under five minutes.
Open the Applications tab, enter a Project Name and a Redirect URL, then hit
Create Application. You’ll instantly receive a client_id.
Every app card exposes its Client ID and Redirect URI, plus a one-click Test URL so you can dry-run the full authorization flow immediately.
Paste the snippet below into your page — or use the Developer SDK tab to generate
a version pre-filled with your own client_id and
redirect_uri.
After authorization the user is redirected back with
#access_token=….
Base64-decode it to obtain the verified profile payload, then clear the fragment from the address bar.
Copy-paste ready — works on any static host.
<!-- MOS ID Client SDK Integration -->
<button id="mosIdMwsBtn">Sign in with MWS</button>
<script>
// 1. MWS Single Sign-On flow (auto-opens the MWS IdP panel)
document.getElementById('mosIdMwsBtn').addEventListener('click', () => {
window.location.href = "https://mwsauth.blogspot.com/?client_id=mos_d3kdgs17y&redirect_uri=https%3A%2F%2Fwww.notepad.us.ci%2F&sso=mws";
});
// 2. Receive and decode the callback credentials
(function handleMosCallback() {
const hash = window.location.hash;
if (hash && hash.includes('access_token=')) {
const params = new URLSearchParams(hash.substring(1));
const token = params.get('access_token');
if (token) {
try {
const profileData = JSON.parse(atob(token));
console.log("Authentication successful! Profile payload:", profileData);
// Dispatch to your application state
alert("Welcome " + profileData.email);
// Clean auth traces from the address bar
window.history.replaceState(null, null, window.location.pathname);
} catch (err) {
console.error("Payload credentials decoding error", err);
}
}
}
})();
</script>
Replace client_id and redirect_uri with the values from your own application card. The sso=mws parameter tells the console to auto-open the MWS identity panel.
Everything shipped in the console, out of the box.
One-click SSO through the MOS Workspace IdP — no password ever leaves your provider.
Per-user base32 secrets issued at enrollment and validated across a ±1 time-step window.
Issue, list and revoke client_id / redirect_uri pairs per project.
Base64 profile payload returned in the URL fragment, ready for atob().
Register, audit and revoke authorised session hardware from one panel.
Enrich profiles with live GitHub metadata, bios and avatars via the public API.
Push real-time authentication events straight to your Telegram handle.
Single-use, expiring codes that atomically promote your workspace plan.
Rotate your passkey directly from the console without the legacy secret.
DiceBear identicon seeds with live preview as you type.
Light, Dark and System modes with a flash-free first paint.
Upstash Redis-backed user and client store with resilient parsing.
Context-aware integration snippets generated per registered app.
Per-record isolation so a single corrupt row can never break the list.
Parameters accepted by the MWS IdP.
mwsauth.blogspot.com
mos_xxxxxxxxx
URL-encoded
mws
base64 JSON
“Invalid Client ID”
The client_id isn’t in the registry. Re-check the Applications tab.
Callback never fires
The redirect_uri must match the registered value exactly — including scheme and trailing slash.
2FA codes rejected
Ensure your device clock is synced — TOTP tolerates only ±30 seconds.
Redeem code rejected
Codes are single-use per account, have a max-use cap and may expire. Check the Upgrade tab.
Our workspace engineers help you wire up SSO, 2FA and audit logging.
Start free, upgrade when your workspace grows. Every plan includes MWS Single Sign-On, the client registry and unlimited developer logins.
Codes are case-insensitive, single-use per account and may expire. Redeeming instantly upgrades your workspace — no card required.
Demo codes have been seeded for testing: MOS-PRO-TRIAL (30 days of Pro) and
MOS-ENT-TRIAL (30 days of Enterprise).
For side projects & prototypes.
For production apps & small teams.
For regulated & large organisations.
Current period: Starter (free tier) · No active paid plan
Applications
0 / 3
Auth Requests
0 / 1,000
Active Devices
1 / 1
Configure your personal and workspace identity parameters.
Directly assign a new passkey without confirming the old password.
Manage identity providers and notification hooks.
MWS Workspace
Not linked
GitHub
Not connected
Telegram Alerts
Not connected
Per-user TOTP secret, verified on every login.
Authorised client hardware instances.