mirror of
https://github.com/zitadel/zitadel.git
synced 2026-07-25 18:28:00 +00:00
194 lines
6.2 KiB
Plaintext
194 lines
6.2 KiB
Plaintext
---
|
|
title: PHP Client
|
|
description: "Integrate ZITADEL Management APIs into PHP applications using supported authentication methods."
|
|
sidebar_label: 'PHP Client'
|
|
---
|
|
|
|
<table>
|
|
<tr>
|
|
<td width="100px">
|
|
<img width="100px" src="/docs/img/tech/php.svg" alt="php logo"/>
|
|
</td>
|
|
<td>
|
|
This guide covers the official Zitadel Management API Client for PHP, which allows you to programmatically manage resources in your Zitadel instance.
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<Callout>
|
|
**This is a Management API Client, not an Authentication SDK.**
|
|
|
|
This library is designed for server-to-server communication to manage your Zitadel instance (e.g., creating users, managing projects, and updating settings). It is **not** intended for handling end-user login flows in your web application. For user authentication, you should use a standard OIDC library with your PHP framework of choice.
|
|
</Callout>
|
|
|
|
The Zitadel PHP Client provides an idiomatic way to access the full gamut of
|
|
Zitadel's v2 Management APIs from your PHP backend.
|
|
|
|
> Please be aware that this client library is currently in an **incubating stage**.
|
|
While it is available for use, the API and its functionality may evolve, potentially introducing
|
|
breaking changes in future updates. We advise caution when considering it for production environments.
|
|
|
|
### Installation
|
|
|
|
You can add the client library to your project using Composer:
|
|
|
|
```bash
|
|
composer require zitadel/client:"^4.0.0-beta1"
|
|
```
|
|
|
|
### Using the SDK
|
|
|
|
Your SDK offers three ways to authenticate with Zitadel. Each method has its
|
|
own benefits—choose the one that fits your situation best.
|
|
|
|
#### 1. Private Key JWT Authentication
|
|
|
|
**What is it?**
|
|
You use a JSON Web Token (JWT) that you sign with a private key stored in a
|
|
JSON file. This process creates a secure token.
|
|
|
|
**When should you use it?**
|
|
|
|
- **Best for production:** It offers strong security.
|
|
- **Advanced control:** You can adjust token settings like expiration.
|
|
|
|
**How do you use it?**
|
|
|
|
1. Save your private key in a JSON file.
|
|
2. Use the provided method to load this key and create a JWT-based
|
|
authenticator.
|
|
|
|
**Example:**
|
|
|
|
```php
|
|
use \Zitadel\Client\Zitadel;
|
|
|
|
$zitadel = Zitadel::withPrivateKey("https://example.us1.zitadel.cloud", "path/to/jwt-key.json");
|
|
|
|
try {
|
|
$response = $zitadel->users->userServiceAddHumanUser([
|
|
'username' => 'john.doe',
|
|
'profile' => [
|
|
'givenName' => 'John',
|
|
'familyName' => 'Doe'
|
|
],
|
|
'email' => [
|
|
'email' => 'john@doe.com'
|
|
]
|
|
]);
|
|
echo "User created: " . print_r($response, true);
|
|
} catch (ApiException $e) {
|
|
echo "Error: " . $e->getMessage();
|
|
}
|
|
```
|
|
|
|
#### 2. Client Credentials Grant
|
|
|
|
**What is it?**
|
|
This method uses a client ID and client secret to get a secure access token,
|
|
which is then used to authenticate.
|
|
|
|
**When should you use it?**
|
|
|
|
- **Simple and straightforward:** Good for server-to-server communication.
|
|
- **Trusted environments:** Use it when both servers are owned or trusted.
|
|
|
|
**How do you use it?**
|
|
|
|
1. Provide your client ID and client secret.
|
|
2. Build the authenticator
|
|
|
|
**Example:**
|
|
|
|
```php
|
|
use Zitadel\Client\Zitadel;
|
|
use Zitadel\Client\Model\UserServiceAddHumanUserRequest;
|
|
use \Zitadel\Client\Model\UserServiceAddHumanUserRequest;
|
|
use \Zitadel\Client\Model\UserServiceSetHumanProfile;
|
|
use \Zitadel\Client\Model\UserServiceSetHumanEmail;
|
|
|
|
$zitadel = Zitadel::withClientCredentials("https://example.us1.zitadel.cloud", "id", "secret");
|
|
|
|
try {
|
|
$response = $zitadel->users->addHumanUser((new UserServiceAddHumanUserRequest())
|
|
->setUsername('john.doe')
|
|
->setProfile(
|
|
(new UserServiceSetHumanProfile())
|
|
->setGivenName('John')
|
|
->setFamilyName('Doe')
|
|
)
|
|
->setEmail(
|
|
(new UserServiceSetHumanEmail())
|
|
->setEmail('john@doe.com')
|
|
));
|
|
echo "User created: " . print_r($response, true);
|
|
} catch (ApiException $e) {
|
|
echo "Error: " . $e->getMessage();
|
|
}
|
|
```
|
|
|
|
#### 3. Personal Access Tokens (PATs)
|
|
|
|
**What is it?**
|
|
A Personal Access Token (PAT) is a pre-generated token that you can use to
|
|
authenticate without exchanging credentials every time.
|
|
|
|
**When should you use it?**
|
|
|
|
- **Easy to use:** Great for development or testing scenarios.
|
|
- **Quick setup:** No need for dynamic token generation.
|
|
|
|
**How do you use it?**
|
|
|
|
1. Obtain a valid personal access token from your account.
|
|
2. Create the authenticator with: `PersonalAccessTokenAuthenticator`
|
|
|
|
**Example:**
|
|
|
|
```php
|
|
use \Zitadel\Client\Zitadel;
|
|
use Zitadel\Client\Zitadel;
|
|
use Zitadel\Client\Model\UserServiceAddHumanUserRequest;
|
|
use \Zitadel\Client\Model\UserServiceAddHumanUserRequest;
|
|
use \Zitadel\Client\Model\UserServiceSetHumanProfile;
|
|
use \Zitadel\Client\Model\UserServiceSetHumanEmail;
|
|
|
|
$zitadel = Zitadel::withAccessToken("https://example.us1.zitadel.cloud", "token");
|
|
|
|
try {
|
|
$response = $zitadel->users->addHumanUser(
|
|
(new UserServiceAddHumanUserRequest())
|
|
->setUsername('john.doe')
|
|
->setProfile(
|
|
(new UserServiceSetHumanProfile())
|
|
->setGivenName('John')
|
|
->setFamilyName('Doe')
|
|
)
|
|
->setEmail(
|
|
(new UserServiceSetHumanEmail())
|
|
->setEmail('john@doe.com')
|
|
)
|
|
);
|
|
echo "User created: " . print_r($response, true);
|
|
} catch (ApiException $e) {
|
|
echo "Error: " . $e->getMessage();
|
|
}
|
|
```
|
|
|
|
---
|
|
|
|
Choose the authentication method that best suits your needs based on your
|
|
environment and security requirements. For more details, please refer to the
|
|
[Zitadel documentation on authenticating service accounts](https://zitadel.com/docs/guides/integrate/service-accounts/authenticate-service-accounts).
|
|
|
|
### Versioning
|
|
|
|
The client library's versioning is aligned with the Zitadel core project. The major version of the
|
|
client corresponds to the major version of Zitadel it is designed to work with. For example,
|
|
v2.x.x of the client is built for and tested against Zitadel v2, ensuring a predictable and stable integration.
|
|
|
|
### Resources
|
|
|
|
- [GitHub Repository](https://github.com/zitadel/client-php): For source code, examples, and to report issues.
|
|
- [Packagist Package](https://packagist.org/packages/zitadel/client): The official package artifact for Composer.
|