DarDevLab learners sign up at dardevlab.com with product-native accounts today. Workspace—DarDev's zero-trust IAM layer and the Authorize step in our platform pipeline—already gates browser-based lab environments for instructor-led cohorts on DarDevCDE. Full single sign-on from dardevlab.com through Workspace into every lab surface is on the roadmap, not a checkbox you can enable in production yet. This guide separates what ships now from what we are building so university partners, enterprise L&D teams, and students know exactly what to expect.
We publish under Deployed Realities. If procurement requires SAML tomorrow, read what ships first and contact DarDev for pilot timing—there is no self-serve toggle yet.
Why SSO matters for a learning platform
Enterprise and faculty buyers object to identity sprawl more often than curriculum gaps. Students juggle university LDAP, GitLab, cloud IDE URLs, and an LMS—each extra password is a dropout point before the first merge request. SSO also drives auditability: who opened a lab namespace, whether access revoked on offboarding, and whether commits map to a directory user. DarDevLab labs require git pushes and pipeline tokens, so Workspace sits in our architecture even while dardevlab.com keeps self-serve signup for Tunisia and MENA learners.
Shipped today: dardevlab.com accounts and lab access
- Account creation and billing stay on dardevlab.com—not replaced by Listmonk or CRM forms
- Email-and-password login with product-managed sessions for self-paced tracks
- GitLab integration per lab: learners fork starter repos and submit merge requests for mentor review
- Optional product-news checkbox on signup that syncs to Twenty CRM and private Listmonk lists when enabled
- Marketing interest for non-customers via mail.dardev.net subscribe forms—separate from lab login
Self-serve students use dardevlab.com plus a GitLab account they link during onboarding. Mentors grade in Git—see hands-on-labs-vs-video for why credentials live in repos, not watch-percentage dashboards.
Shipped today: Workspace SSO on DarDevCDE cohort paths
Instructor-led cohorts run on DarDevCDE—browser VS Code on Kubernetes. Workspace handles SSO there: one login, session scoped to the cohort namespace, no local Docker install. DarDevOps provisions quotas; egress is monitored at ingress per browser-vscode-security. This matches the Authorize step in workspace-authorize-step. Cohort pilots inherit the stack when DarDev hosts labs—not when a student only reads static modules. See cde-training-cohorts-demos for intake logistics. Cohort Workspace login does not yet unify with a standalone dardevlab.com profile.
On the roadmap: unified DarDevLab + Workspace login
We are integrating dardevlab.com with Workspace so one identity can span the lab portal, DarDevCDE workspaces, and shared GitLab group membership without manual linking. Planned work includes OIDC login on dardevlab.com, enterprise SAML for university and corporate IdPs, just-in-time cohort provisioning, centralized session revocation on offboarding, and a migration path for existing password accounts.
- OIDC bridge: dardevlab.com delegates authentication to Workspace while preserving product entitlements
- SAML metadata exchange for ENIT-style faculty pilots and enterprise L&D buyers
- Automatic GitLab group invites keyed off Workspace group membership
- Audit exports: lab open events correlated to directory user IDs
- Self-serve migration path for existing dardevlab.com password accounts
Timelines depend on pilot feedback. For SAML on a fixed intake date, scoping via dardev.net beats waiting for a product banner. Early partners get beta labels and runbook access.
What we are not building
Workspace covers DarDev products and integrations we operate—not your HRIS. Cold marketing contacts never become lab accounts via CRM imports. GitLab stays the git surface; SSO reduces login friction, it does not hide repos from employers.
How buyers should evaluate now
Self-serve learners: use dardevlab.com—GitLab setup is part of the curriculum (dardevlab-certification-tracks). Enterprise cohorts: confirm DarDevCDE hosting (Workspace SSO live), whether you need SAML on the portal itself (roadmap), and GitLab onboarding until group automation ships. Honest answers on discovery prevent demo-day surprises when procurement assumed portal SAML was already live.
SSO serves shipping engineers, not RFP checkboxes alone. Start at dardevlab.com for self-paced tracks or contact dardev.net/products when you need a cohort identity pilot scoped before intake.
Can I log in to dardevlab.com with my company SAML IdP today?
Not on the self-serve portal yet. Enterprise SAML is on the Workspace integration roadmap. DarDevCDE-hosted cohorts already use Workspace SSO—confirm with DarDev before your intake date.
Is DarDevLab login the same as my DarDevCDE workspace?
Not always. Self-paced dardevlab.com accounts and cohort DarDevCDE workspaces can coexist as separate identities until unified OIDC login ships. Pilots document which path your program uses.
Does SSO replace GitLab accounts for labs?
No. Labs remain git-based with GitLab merge requests. Roadmap work automates group membership; it does not remove the repos employers evaluate.
How does signup relate to CRM and marketing email?
Product signup stays on dardevlab.com. Optional news opt-in syncs to Twenty CRM tags and private Listmonk lists. Marketing-only subscribers use mail.dardev.net forms—they are not lab accounts.
Who should contact DarDev about SSO pilots?
University partners and enterprise L&D teams planning cohort intakes. Use dardev.net contact for scoping; self-serve learners can start on dardevlab.com without waiting for SAML. Include your IdP type and intake date in the first message.
