better sso troubleshooting info

Author: lovasoa

examples/official-site/sso/single_sign_on.md

@@ -113,8 +113,19 @@ When deploying to production:
 
 ## Troubleshooting
 
-- If login fails, check that the redirect URI matches exactly
-- Verify that your client ID and secret are correct
-- Make sure your `host` setting matches your application's URL
-- For local development, use `http://localhost:8080` as the host
-- For production, use your actual domain name
+### Version Requirements
+- OIDC support requires SQLPage **version 0.35 or higher**. Check your version in the logs.
+
+### Common Configuration Issues
+- **Redirect URI Mismatch**: The redirect URI in your OIDC provider settings must exactly match `https://your-domain.com/sqlpage/oidc_callback` (or `http://localhost:8080/sqlpage/oidc_callback` for local development)
+- **Invalid Client Credentials**: Double-check your client ID and secret are copied correctly from your OIDC provider
+- **Host Configuration**: The `host` setting in `sqlpage.json` must match your application's domain name exactly
+- **HTTPS Requirements**: Most OIDC providers require HTTPS in production. Ensure your site is served over HTTPS.
+- **Provider Discovery**: If SQLPage fails to discover your provider's configuration, verify the `oidc_issuer_url` is correct and accessible by loading `{oidc_issuer_url}/.well-known/openid-configuration` in your browser.
+
+### Debugging Tips
+- Check SQLPage's logs for detailed error messages. You can enable verbose logging with the `RUST_LOG=trace` environment variable.
+- Verify your OIDC provider's logs for authentication attempts
+- In production, confirm your domain name matches exactly in both the OIDC provider settings and `sqlpage.json`
+- If [using a reverse proxy](/your-first-sql-website/nginx.sql), ensure it's properly configured to handle the OIDC callback path.
+- If you have checked everything and you think the bug comes from SQLPage itself, [open an issue on our bug tracker](https://github.com/sqlpage/SQLPage/issues).

examples/single sign on/README.md

@@ -42,7 +42,8 @@ the [CAS protocol](https://apereo.github.io/cas/) (version 3.0), which is mostly
 OIDC is an authentication protocol that allows users to authenticate with a third-party identity provider and then access applications without having to log in again. This is useful for single sign-on (SSO) scenarios where users need to access multiple applications with a single set of credentials.
 OIDC can be used to implement a "Login with Google" or "Login with Facebook" button in your application, since these providers support the OIDC protocol.
 
-SQLPage has built-in support for OIDC authentication. This project demonstrates how to use it with the free and open source [Keycloak](https://www.keycloak.org/) OIDC provider.
+SQLPage has built-in support for OIDC authentication since v0.35.
+This project demonstrates how to use it with the free and open source [Keycloak](https://www.keycloak.org/) OIDC provider.
 You can easily replace Keycloak with another OIDC provider, such as Google, or your enterprise OIDC provider, by following the steps in the [Configuration](#configuration) section.
 
 ### Important Note About OIDC Protection