aasdasdasdas

@dockal.dev řekl v Chyba při implementaci: dockal.dev Nov 1, 2021, 2:35 AM Hello, I would like to implement a Login List, but I am encountering a problem with obtaining an access token from "code" Sometimes I get an error right after generating the code { "message": "ticket expired", "status": 466 } and sometimes again {"error": "invalid_grant"} Thank you for your response. This error usually occurs when the authorization code expires quickly or is reused. Make sure you exchange the code immediately and verify your redirect URI and client details are correct. I faced a similar issue in an iOS flow where delay caused “invalid_grant” errors noticed this while working with delta ios executor related setups, and using a fresh code each time fixed it.

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