Dependency-light PHP authentication starter for Tuurio ID with secure sessions and OpenID Connect Authorization Code flow.
Generated from
Tuurio/auth_samples/auth_samples_php. Submit implementation fixes upstream so they are not replaced by the next synchronized release.
- Standards-based OpenID Connect authentication with framework-native integration.
- Exact redirect and post-logout redirect handling.
- Protected-route and logout examples.
- A reviewed, pinned Tuurio provisioning workflow.
- Create a repository with Use this template or clone this repository.
- Follow the framework-specific prerequisites below.
- Review and run this pinned provisioning command:
npx manage-tuurio-id@1.1.6 init --framework php --project-dir . --auth browser --yes --output json --campaign github_php --no-open --no-wait- Approve the exact command, then complete the secure browser handoff yourself.
- Run the build and verify one real sign-in and sign-out.
Never paste credentials, client secrets, authorization codes, tokens, session cookies, or environment-file contents into an agent chat. Browser and native applications are public clients and must not contain a client secret.
- Runtime: PHP 8.2+
- Package manager: None
- Verification:
find . -name '*.php' -print0 | xargs -0 -n1 php -l
This starter uses OpenID Connect Authorization Code flow. Browser and native clients use PKCE S256 and contain no client secret. Redirect and post-logout redirect URIs must match exactly. Identity comes from the established OIDC integration or an authenticated UserInfo request; decoded JWT payloads are never treated as validation. Keep generated local environment files ignored and never commit tokens or credentials.
A server-rendered PHP demo that signs in with OAuth 2.0 / OpenID Connect, keeps tokens server-side, and supports logout.
- Detailed integration guide: PHP example page
- General developer docs: Tuurio ID developers
cd auth_samples_php
cp .env.example .env
# edit .env with your tenant/client values
php -S localhost:8080 -t public router.phpOpen http://localhost:8080.
For Apache/Plesk deployments, public/ is still the preferred document root. If the whole package is web-accessible instead, the bundled root .htaccess forwards requests into public/ and blocks direct access to internal files.
Configure your Tuurio client with these redirect URLs (matching your .env values):
Redirect URI: http://localhost:8080/auth/callback
Post-logout Redirect URI: http://localhost:8080/logout/callback
TUURIO_ISSUER=https://YOUR_TENANT.id.tuurio.com
TUURIO_CLIENT_ID=YOUR_CLIENT_ID
TUURIO_CLIENT_SECRET=
TUURIO_REDIRECT_URI=http://localhost:8080/auth/callback
TUURIO_POST_LOGOUT_REDIRECT_URI=http://localhost:8080/logout/callback
TUURIO_SCOPE=openid profile emailValues come from your Tuurio Connect page:
https://<tenantId>.id.tuurio.com/admin/clients
Licensed under the Apache License, Version 2.0. See LICENSE.