Configuration report

Awthy's configuration report gives site administrators and support a compact view of the current security setup. Open Awthy > Reporting > Diagnostics in WordPress to generate it.

Which report should I copy?

Use Copy support report when opening or updating a support ticket. This redacted report is designed to be pasted into a ticket and includes useful environment, license, policy, feature-state, and reporting information.

The full internal report is for authorized site administrators investigating a problem internally. Awthy requires an explicit acknowledgement before it can be copied because it contains more operational detail. Do not paste the internal report into a public issue, chat, or ordinary support ticket.

What Awthy leaves out

The support report intentionally excludes secrets and identifying operational data, including:

passwords, nonces, cookies, recovery links, TOTP secrets, backup codes, and passkey challenges;
OAuth client secrets, license keys, Hub signing secrets, webhook signing secrets, and export credentials;
webhook URLs, full callback URLs, full IP addresses, and full user agents;
customer, order, and account records.

Provider, webhook, and export configuration is represented using safe counts, types, labels, and enabled states. Always scan copied text before sharing it, and remove anything specific to your organization that you do not want in the ticket.

Support workflow

Support should ask for the support report, not screenshots of every settings page. The report is easier to search and compare while reducing the chance that a screenshot captures unrelated personal or secret information.

If the report cannot be generated, include the visible error message and use the smaller System diagnostics report from Awthy Settings. Never send credentials or recovery material to support.