Single Sign-On & Identity

One identity provider for every staff login: a clean directory, apps connected through SAML or OIDC, automated provisioning, and the routines that keep accounts consistent and sign-in working.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Single Sign-On & Identity, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🔐 IT & Security

Single Sign-On & Identity

Centralising staff identities and logins in one identity provider, connecting apps through single sign-on and keeping accounts consistent.

  1. Map of every login and account store in use
  2. Choosing a workforce identity provider
  3. Deciding the authoritative source for staff records
  4. Username and sign-in name convention
  5. Identity attribute dictionary
  6. Group model for app assignment
  7. Break-glass accounts for the identity provider
  8. Identity provider administrator roles and delegation
  9. Pilot wave of five apps on single sign-on
  10. Single sign-on app catalogue with named owners
  11. Monthly directory data quality sweep
  12. SAML certificate and secret expiry calendar
  13. Weekly sign-in log review
  14. Change control for identity provider configuration
  15. Provisioning sync error triage
  16. Sweep for accounts that bypass single sign-on
  17. Identity provider release notes watch
  18. Quarterly identity health report
  19. SAML 2.0 for administrators
  20. OpenID Connect and OAuth flows for app owners
  21. SCIM provisioning in a test tenant
  22. Troubleshooting a failed SSO login with browser tools
  23. Active Directory essentials for cloud-first admins
  24. Sessions, token lifetimes and single logout
  25. How attackers abuse identity providers
  26. Automated provisioning for the ten largest apps
  27. Session length and re-authentication policy
  28. Self-service password reset that resists takeover
  29. Help desk identity check before resets
  30. Options for legacy apps without SAML or OIDC
  31. Negotiating SSO pricing with SaaS vendors
  32. Turning off password login once SSO is enforced
  33. Hybrid directory sync design
  34. Retiring the old directory after cutover
  35. Identity provider migration cutover
  36. Company email domain change across identities
  37. Identity provider outage rehearsal
  38. Staff launch of the new sign-in experience
  39. Small business SSO with the office suite you already pay for
  40. Contractor and agency identities with sponsors and end dates
  41. Partner and guest access through federation
  42. Merging identity directories after an acquisition
  43. Engineers into cloud consoles through SSO
  44. Enforcing SSO on code hosting and CI tools
  45. Frontline and shared-device worker identities
  46. Identity provider configuration as code
  47. Service accounts and API tokens in the identity provider
  48. Short-lived SSH and Kubernetes credentials from SSO
  49. Monitoring federation trusts for tampering
  50. Hub federation across several identity providers

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Map of every login and account store in use

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most organisations that think they have one directory actually have five: a Microsoft or Google tenant, an old on-premises Active Directory, the HR system, and dozens of apps holding their own usernames and passwords.

First tasks

  • List the directories and tenants you already administer, with their admin URLs
  • Export a year of software charges from finance and add every app found
  • Record the sign-in method and admin owner for each app on the list
  • Flag the ten apps that hold customer, financial or HR data

Choosing a workforce identity provider

The identity provider becomes the front door to every app, so switching later is a multi-month migration nobody wants. Comparing two or three serious candidates against your real app list, directory, device estate and budget, rather than a feature grid, means the choice holds for the next five years.

First tasks

  • Write the requirements list from the account store map
  • Shortlist three providers and request trial tenants
  • Connect your three hardest apps to each trial tenant
  • Record the decision with pricing tier and reasons the others lost

Deciding the authoritative source for staff records

Accounts drift when two systems both think they own a person's name, title and manager. Deciding that the HR system creates people and the identity provider creates logins, or the reverse for a small team without HR software, settles every later argument about which record is right.

First tasks

  • List the core identity fields and where each one is edited today
  • Book a 45-minute session with the HR lead to agree field ownership
  • Draw the sync direction between HR, directory and identity provider
  • Write the correction rule and get both leads to sign it

Make it yours.

Install Single Sign-On & Identity, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.