Get help
Start with troubleshooting and identify the first stage that fails: application entry, hosted page, callback, session check, API permission check or Account Security navigation.
Configuration or feature availability
Section titled “Configuration or feature availability”Ask your Oathvera workspace administrator to confirm the selected environment, client type, registered destinations and enabled methods in the Oathvera dashboard. Use your established Oathvera onboarding/support channel for platform issues.
If you do not yet have a workspace or support contact, visit Oathvera to begin onboarding. These docs do not promise a support response-time SLA.
Include in an integration report
Section titled “Include in an integration report”- Documentation release and page URL.
- Backend/framework/runtime versions and browser/OS.
- Sandbox or Production and the operation that failed.
- Timestamp with timezone, HTTP status and safe error code.
- Your application-generated correlation reference.
- Expected behavior, actual behavior and minimal redacted reproduction steps.
Do not include client secrets, tokens, cookies, passwords, private keys, recovery codes or full callback URLs. Redact state, intent, challenge, completion handles and personal information.
Report a documentation problem
Section titled “Report a documentation problem”Send the page URL, the unclear instruction and the result you expected through the same support channel. A screenshot should show only the relevant public documentation or a redacted error.
For an urgent authentication issue, follow your organization’s incident process and contact your existing Oathvera representative. Do not publish customer credentials in a public issue.