[imit]

Mirrors the Python SDK change.

users.find_by_identifier

• It now searches the app's users with the secret key (the user list, GET /v1/:app_id/users with q, limit=100, page) and keeps only an exact match:
  • the email in any case;
  • the phone number compared as digits (include the country code).
• q is a loose search, so it can answer near-identical users; they don't count.
• It follows next_page for up to 10 pages.
• It returns nil when nobody by that identifier uses the app, and never creates a user.
• A blank identifier (or a phone with no digits) makes no call.
• Same signature. The result is the user as users.get shows it.
• Unit tests: the fake API gets a loose user list that pages by 2. The tests cover an exact match on a later page, phones in any format, near misses, the page limit, and no call for a blank identifier.

Sessions

sessions.list and sessions.revoke work with the secret key alone, no user session needed. The docs, README and CHANGELOG say so.

Live suite

The examples that were pending on API behavior are normal examples again:

• listing and revoking sessions;
• a refreshed token verifying locally;
• find_by_identifier answering nil for nobody (and making nobody).

A new example checks the exact match against the real, loose search, by email (in another case) and by phone (formatted differently).

Results:

• bundle exec rake live against scute-api-v2 v23: 74 examples, 0 failures, 1 pending. The pending one is a skip: scute-ruby has no local decision engine for the policy snapshot.
• Unit suite: 84 examples, 0 failures. RuboCop is clean.

After the run, the suite's app has no users, agents, properties or policy left, and its settings are back to their defaults.