application id not found is Entra ID error AADSTS700016: the application ID in your auth request does not exist in the tenant the request targets. The app is usually single-tenant and registered in a different directory, or the client ID was copied wrong. Check the app registration home tenant, make the app multi-tena…
Fixes the the identity platform failure "AADSTS50011 access review sign-in failed: reply URL specified in the request does not matc" by acting on the exact message, proving the fix on one item, then rerunning and reconciling counts. Use when this error blocks an export, review or check. Not for platform outages or per…
Vectle found the following relevant skills: - AADSTS50011 access review sign-in failed: reply URL specified in the request does not match - AADSTS50011 "the reply URL specified in the request does not match" entra sso fix
Fixes the the identity platform failure "AADSTS50011 access review sign-in failed: reply URL specified in the request does not matc" by acting on the exact message, proving the fix on one item, then rerunning and reconciling counts. Use when this error blocks an export, review or check. Not for platform outages or per…
Vectle found the following relevant skills: - AADSTS50011 "the reply URL specified in the request does not match" entra sso fix - AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application
Vectle found the following relevant skills: - how to investigate a suspicious OAuth app grant - how to revoke oauth app grants for a terminated user - [xero-node OAuth cal…
Vectle found the following relevant skills: - AADSTS7000218: the request body must contain client_secret or client_assertion - Azure Key Vault secrets in Node.js: SecretClient with @azure/identity
Vectle found the following relevant skills: - AADSTS50011 "the reply URL specified in the request does not match" entra sso fix - AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application
Fixes JupyterHub OAuth callback failures with a state mismatch when running behind a reverse proxy. Use when login redirects loop or the callback rejects the state parameter. Not for allow-list 403s or spawn errors.
Fixes Typeform OAuth flows failing because the authorization code was exchanged twice, by making the exchange single-shot and fetching a fresh code. Not for redirect URI errors, and not for refresh token problems.
Vectle found the following relevant skills: - Linear OAuth: token endpoint returns 503, then 400 invalid_grant on every retry - oauth2: "invalid_grant" "Malformed auth code."
Fixes Calendly OAuth authorize failures with invalid_scope by correcting the requested scopes against Calendly's current scope list. Not for redirect URI errors, and not for token problems after authorization succeeds.
Fixes Linear OAuth authorize failures caused by a redirect URI that is not registered in the Linear app's OAuth settings. Not for token-exchange errors, and not for scope problems.
Vectle found the following relevant skills: - Oauth error invalid_request: The redirect_uri is not whitelisted (Shopify app install) - Failed exchange at /oauth/token - code_verifier, redirect_uri, and one-time codes
Vectle found the following relevant skills: - azure ad saml error aadsts50105 user not assigned - agent failed to parse the vault response: wrapped token payload error - […
Vectle found the following relevant skills: - infobip-api-php-client: createWhatsAppTemplate fails with Invalid request body (category missing) - python client to AWS Elasticsearch: requests must be SigV4-signed