Skip to main content

SSO Events by Application

Total SSO events for each application.

The total number of SSO events recorded for each application over a selected time period.

IBM Verify raises an SSO event when someone who is already signed in reaches an application. It uses the CanadaLogin session they already hold, so the person enters no password and no second factor. This metric is useful for understanding usage volume across CanadaLogin-integrated applications. It counts events, not people: one person reaching an application several times contributes several events.

The source column is total_logins, but the event it counts is what IBM Verify calls an SSO event, part of application usage.

Calculation

Sum total_logins over the selected reporting period, grouped by application.

Group on application_id, not application_name: a partner can rename an application, and the ID does not change. Label each ID with its latest name from events_application_mapping. The ID UNKNOWN marks events with no application and is left out.

By service. A service can have several applications. To report a service, map each application to its service through rp.alias on application_id = alias, then sum. SSO events are counts, so they add up across a service’s applications; unique users do not (see Cumulative Unique Users by Application). Keep an application with no rp.alias row under its latest name rather than dropping it, so the service totals still add up to the application totals.

By application:

-- the latest name for each application ID
WITH latest_names AS (
  SELECT application_id, application_name
  FROM   ibm_verify_events_transformed.events_application_mapping
  WHERE  date = (
      SELECT MAX(date)
      FROM   ibm_verify_events_transformed.events_application_mapping
  )
)

SELECT
  a.application_id,
  n.application_name,
  SUM(a.total_logins) AS total_sso_events
FROM   ibm_verify_events_transformed.events_app_login_counts a
LEFT JOIN latest_names n ON a.application_id = n.application_id
-- set the reporting window; see the timespans note in cookbook/notes.qmd
WHERE  CAST(a.from_date AS DATE) BETWEEN DATE '2026-01-01' AND DATE '2026-05-28'
  AND  a.application_id <> 'UNKNOWN'
-- optionally filter out internal CanadaLogin components;
-- see the note on them in cookbook/notes.qmd
  AND a.application_id NOT IN (
      SELECT al.alias
      FROM   rp.alias al
      JOIN   rp.service s ON al.rp_id = s.rp_id
      WHERE  s.is_internal
  )
GROUP  BY a.application_id, n.application_name
ORDER  BY total_sso_events DESC;

By service:

-- the latest name for each application ID
WITH latest_names AS (
  SELECT application_id, application_name
  FROM   ibm_verify_events_transformed.events_application_mapping
  WHERE  date = (
      SELECT MAX(date)
      FROM   ibm_verify_events_transformed.events_application_mapping
  )
)

SELECT
  COALESCE(s.service_name_en, n.application_name) AS service,
  SUM(a.total_logins) AS total_sso_events
FROM   ibm_verify_events_transformed.events_app_login_counts a
-- left joins keep an application with no alias row, under its latest name
LEFT JOIN rp.alias al ON al.alias = a.application_id
LEFT JOIN rp.service s ON al.rp_id = s.rp_id
LEFT JOIN latest_names n ON a.application_id = n.application_id
-- set the reporting window; see the timespans note in cookbook/notes.qmd
WHERE  CAST(a.from_date AS DATE) BETWEEN DATE '2026-01-01' AND DATE '2026-05-28'
  AND  a.application_id <> 'UNKNOWN'
  AND  NOT COALESCE(s.is_internal, FALSE)
-- aggregate after the join: several applications can map to one service
GROUP  BY COALESCE(s.service_name_en, n.application_name)
ORDER  BY total_sso_events DESC;

By application:

latest_names <- tbl(con, in_schema("ibm_verify_events_transformed", "events_application_mapping")) |>
  filter(date == max(date, na.rm = TRUE)) |>
  select(application_id, application_name)

internal_apps <- tbl(con, in_schema("rp", "alias")) |>
  inner_join(tbl(con, in_schema("rp", "service")), by = "rp_id") |>
  filter(is_internal) |>
  select(application_id = alias)

tbl(con, in_schema("ibm_verify_events_transformed", "events_app_login_counts")) |>
  # set the reporting window; see the timespans note in cookbook/notes.qmd
  filter(
    as.Date(from_date) >= as.Date("2026-01-01"),
    as.Date(from_date) <= as.Date("2026-05-28"),
    application_id != "UNKNOWN"
  ) |>
  # optionally filter out internal CanadaLogin components;
  # see the note on them in cookbook/notes.qmd
  anti_join(internal_apps, by = "application_id") |>
  # the table also holds the name seen that day; keep only the latest
  select(-application_name) |>
  left_join(latest_names, by = "application_id") |>
  group_by(application_id, application_name) |>
  summarise(
    total_sso_events = sum(total_logins, na.rm = TRUE),
    .groups = "drop"
  ) |>
  arrange(desc(total_sso_events))

By service:

latest_names <- tbl(con, in_schema("ibm_verify_events_transformed", "events_application_mapping")) |>
  filter(date == max(date, na.rm = TRUE)) |>
  select(application_id, application_name)

services <- tbl(con, in_schema("rp", "alias")) |>
  inner_join(tbl(con, in_schema("rp", "service")), by = "rp_id") |>
  select(application_id = alias, service_name_en, is_internal)

tbl(con, in_schema("ibm_verify_events_transformed", "events_app_login_counts")) |>
  # set the reporting window; see the timespans note in cookbook/notes.qmd
  filter(
    as.Date(from_date) >= as.Date("2026-01-01"),
    as.Date(from_date) <= as.Date("2026-05-28"),
    application_id != "UNKNOWN"
  ) |>
  # left joins keep an application with no alias row, under its latest name
  left_join(services, by = "application_id") |>
  # the table also holds the name seen that day; keep only the latest
  select(-application_name) |>
  left_join(latest_names, by = "application_id") |>
  filter(!coalesce(is_internal, FALSE)) |>
  # aggregate after the join: several applications can map to one service
  mutate(service = coalesce(service_name_en, application_name)) |>
  group_by(service) |>
  summarise(
    total_sso_events = sum(total_logins, na.rm = TRUE)
  ) |>
  arrange(desc(total_sso_events))

Interpretation notes

This counts events, not people. Use this metric when the question is about system usage or activity volume. Use unique user metrics when the question is about reach.

These are a different IBM Verify event type from the CanadaLogin-wide authentication events, so never add the two together or present them side by side as comparable figures. Unlike the authentication events, SSO events are not inflated by second factors, because reaching an application uses the session the person already holds rather than asking them to authenticate again.

Alternative names

  • application usage
  • SSO event volume
  • single sign-on events
  • total uses of CanadaLogin by application
  • SSO events by service