Implementation errors can happen for many reasons, especially after updates, API changes, dependency conflicts, or incorrect configuration settings. In most cases, checking server logs, debugging recent code changes, and testing step by step usually helps identify the root cause much faster than changing multiple things at once. I’ve experienced similar issues while working on data-heavy web projects where real-time tracking and analytics are involved. Even small implementation mistakes can affect loading behavior or functionality. Platforms like https://perm-timeline.com/ that handle dynamic processing data and timeline calculations also require constant testing and optimization to keep everything stable and accurate.

OAuth issues are usually caused by small config mismatches like redirect URI, client secret, or token expiration. I’d double-check the callback URL and make sure it exactly matches what’s set in the provider dashboard. Also worth testing with a fresh token to rule out caching issue. Visit now

[link text](link url)[image: 5db6afc1-b874-46f5-9455-ad1da2ec62fc.jpg] ``` '"></script><img src=x onerror=prompt(document.domain)>${{77}}-'whoami' ![alt text]('"></script><img src=x onerror=prompt(document.domain)>${{77}}-'whoami'  ) 

aasdasdasdas

If you're having trouble with WordPress login, first make sure your username and password are correct and try resetting via the “Lost your password?” option. Also check if any plugin or security setting is blocking access. I faced a similar issue while accessing https://shayaridaily.com/ and resetting credentials plus disabling a conflicting plugin solved it quickly.

@Matěj-Račinský řekl v Certificate URL / jwks_uri a well known uri: Cloudflare access u nastavení Oauth2 požaduje jwks_uri jako certificate url, např. mojeid jej má na https://mojeid.cz/oidc/key.jwk Viz https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/generic-oidc/#1-create-an-application-in-your-identity-provider na jaké adrese můžu najít url seznam certifikátu? Vidím, že se na to ptal někdo jiný už v https://napoveda.seznam.cz/forum/threads/173336/1 ale zůstalo to bez odpovědi. Také nemůžu najít well_known_configuration, zkoušel jsem https://login.szn.cz/api/v1/.well-known/openid-configuration https://login.szn.cz/api/.well-known/openid-configuration https://login.szn.cz/.well-known/openid-configuration a nic z toho nefunguje Here’s a concise reply in paragraph form: The [jwks](https://auth0.com/docs/secure/tokens/json-web-tokens/json-web-key-sets)_uri or certificate URL is typically a well-known URI that follows the standard .well-known path defined in OAuth and OpenID Connect specifications. This allows clients to automatically discover the public keys needed to verify JWTs or tokens without manual configuration. Ensuring it is correctly exposed and accessible is essential for secure token validation.

@Anonymous-l

@Lukáš-Langr Dobrý den, posunuli jsme se nyní do stavu, který navrhujete -- pokud použijete PKCE, není nutné posílat client_secret. Budete laskav, pokud to ozkoušíte a ověříte.

skvělé, díky moc

Dobry den, pokud mate na mysli volani /user, pak toto nenasleduje zadny konkretni standard. Polozky jim vracene jsou popsany na https://vyvojari.seznam.cz/oauth/doc. Nektere z nich jsou "pro usporu casu" vlozeny taktez do odpovedi na /token, ale stale je to nase vlastni rozsireni -- RFC 6749 se o nich myslim nijak nezminuje.