Chapter 14 — Troubleshooting sign-in problems

Chapter 14 — Troubleshooting sign-in problems

Lesson map

Lesson 14 published. Map, example, EX053.

flowchart TD
  N0["Learning outcomes"]
  N1["14.1 A method"]
  N2["14.2 Using logs"]
  N3["14.3 Communicating"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX053"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["14.1 A method"]
  N2["14.2 Using logs"]
  N3["14.3 Communicating"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX053"]

[Learning outcomes]
    |
    v
[14.1 A method]
    |
    v
[14.2 Using logs]
    |
    v
[14.3 Communicating]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX053]

Learning outcomes

You will (1) follow a troubleshooting method; (2) use logs to find causes; (3) communicate with affected staff.

14.1 A method

When a dentist cannot sign in, Tomas follows a method: confirm the symptom and when it started; check whether others are affected; read the sign-in log entry for the failure reason; form one hypothesis and test it; fix and confirm with the user; record the cause. Following steps prevents guessing, such as resetting a password when the real problem is an expired device certificate, which wastes time and can introduce new problems for the user. Tomas writes the method on one card beside the IT desk.

14.2 Using logs

The log shows the dentist's sign-in failed because the device was no longer compliant: its operating system update was overdue. Tomas guides the update, the device becomes compliant and sign-in works. Another day several staff fail at once; the log shows a SAML certificate error, and the expiry date confirms the certificate lapsed overnight. He renews it with the supplier and adds expiry to the calendar. The log's failure reason usually points straight at the cause. He records both causes in the troubleshooting log for future reference.

14.3 Communicating

During the certificate outage Tomas tells both surgeries what is wrong, the expected fix time and the paper fallback for appointments. He updates them when sign-in returns. Afterwards he writes a short note explaining the cause and the calendar reminder that prevents a repeat. Clear communication reduces pressure on reception, who face patients, and builds trust that IT problems are understood and handled rather than hidden. Priya reviews the note and suggests adding the time each update was sent. Tomas adds a short template for future outage messages so updates can be sent quickly and consistently.

Worked example

A non-compliant device and an expired SAML certificate are diagnosed from log failure reasons; the outage lasts 40 minutes with updates throughout.

Synthetic case. Incidents and timings are synthetic.

Errors and limits

Resetting passwords by reflex wastes time when the cause is device compliance or certificates.

Exercises

• EX053 — First step. What is the first troubleshooting step? Rubric: 3 = confirm the symptom and when it started;; 2 = confirm;; 1 = reset;; 0 = none.
• EX054 — Dentist cause. Why did the dentist's sign-in fail? Rubric: 3 = device not compliant, overdue update;; 2 = compliance;; 1 = password;; 0 = none.
• EX055 — Group outage. What caused the group failure? Rubric: 3 = expired SAML certificate;; 2 = certificate;; 1 = network;; 0 = none.
• EX056 — Prevention. What prevents a repeat certificate outage? Rubric: 3 = calendar reminder for expiry;; 2 = reminder;; 1 = vague;; 0 = none.

Synthesis

A step-by-step method guided by log failure reasons, with clear communication, resolves sign-in problems quickly.

Continue studying — chapter 14 of 18

← Chapter 13 (draft) · Course chapter index · Chapter 15 (draft) →