The guide gains two sources that need no password from anyone:
Microsoft 365: tenant, app (client) id and client secret. The run uses import exchange-graph --app-only --user {email}. Check signs the app in and reads the token's roles, naming any Graph application permission it lacks.
Google Workspace: the path to a service account's JSON key. The run uses import imap --url imaps://imap.gmail.com --google-key FILE --auth-user {email}. Check asks Google for a token for the first account in the list.
Also:
JwtClaims.roles, read from the token.
The service-account key helper moves into tests/integration/google.rs, so mock_imap and mock_guide share it.
Updates to docs/usage.md and the CHANGELOG.
Tested: fmt, clippy -D warnings, the full suite, a new mock test for the Google check, and unit tests for the new sources. I looked at both forms in a browser. Neither has been tried against a real tenant.
The guide gains two sources that need no password from anyone:
- **Microsoft 365**: tenant, app (client) id and client secret. The run uses `import exchange-graph --app-only --user {email}`. Check signs the app in and reads the token's roles, naming any Graph application permission it lacks.
- **Google Workspace**: the path to a service account's JSON key. The run uses `import imap --url imaps://imap.gmail.com --google-key FILE --auth-user {email}`. Check asks Google for a token for the first account in the list.
Also:
- `JwtClaims.roles`, read from the token.
- The service-account key helper moves into `tests/integration/google.rs`, so `mock_imap` and `mock_guide` share it.
- Updates to `docs/usage.md` and the CHANGELOG.
Tested: fmt, clippy `-D warnings`, the full suite, a new mock test for the Google check, and unit tests for the new sources. I looked at both forms in a browser. Neither has been tried against a real tenant.
Microsoft 365 reads every mailbox as an Entra app with a client secret
(--app-only); Check signs the app in and names any Graph application
permission it lacks. Google Workspace reads Gmail as a service account
with domain-wide delegation (--google-key); Check asks Google for a token
for the first account.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The guide gains two sources that need no password from anyone:
import exchange-graph --app-only --user {email}. Check signs the app in and reads the token's roles, naming any Graph application permission it lacks.import imap --url imaps://imap.gmail.com --google-key FILE --auth-user {email}. Check asks Google for a token for the first account in the list.Also:
JwtClaims.roles, read from the token.tests/integration/google.rs, somock_imapandmock_guideshare it.docs/usage.mdand the CHANGELOG.Tested: fmt, clippy
-D warnings, the full suite, a new mock test for the Google check, and unit tests for the new sources. I looked at both forms in a browser. Neither has been tried against a real tenant.