# OpenID Connect authentication
If you're a Control Center administrator, you can use Control Center to add and manage OpenID Connect (OIDC) authentication configurations for an organization. OIDC for Servers is the preferred way to authenticate with the Pismo platform. It provides greater security guarantees in service communications than basic authentication using client credentials. In addition, OpenID Connect supports multi-tenancy, allowing for multiple tenants to run in a single instance of the application while keeping their configurations and data isolated.
> ๐ Dual approval
>
> If your company is using the dual approval feature (beta release), creating, editing, or deactivating an OpenID authentication configuration requires approval. With dual approval, you initiate the change and submit a request for approval. A second person must review and approve it. The change doesn't take effect until the request is approved.
>
> For more information about dual approval, refer to [Dual approval](https://developers.pismo.io/pismo-docs/docs/dual-approval).
# Create OpenID authentication configuration
To add an OpenID authentication configuration to an organization, you must provide a public encryption key for use when authenticating with the Pismo platform. You also must specify one of the following authentication types:
* **Standard**โGives the organization access to all Pismo endpoints that the customer has access to. It is managed internally by the Pismo platform.
* **Third-party**โGives access to selected Pismo endpoints, based on OIDC permission groups. This method is typically managed for you by a third-party provider and is not available through the Pismo Call Center.
| Field | Description | Example |
|---|---|---|
| Tenant ID | Organization ID | `tn-123456-A789-42A2-8B0E-2052D05577D7` |
| auth\_type | Authentication type | `STANDARD` (the `THIRD_PARTY` type is not available in the current release) |
| Status | Status of the authentication configuration | ACTIVE |
| public\_key | Public encryption key used for authentication | \----BEGIN CERTIFICATE----\ MIIEajCCAtKgAwIBAgIQaA1mKgVN/KPB4gLfCWcDUDADCpyb2\ . . .\ \----END CERTIFICATE----- |
| created\_at | Timestamp when the authentication configuration was created | 9/13/24 14:58 |
| update\_at | Timestamp when the authentication configuration was last updated | 9/13/24 14:58 |
| signer\_audience | Audience for the signer | Can be an ID or a URL |
| signer\_issuer | Issuer for the signer | Can be an ID or a URL |
| verifier\_audience | Audience for the verifier | Can be an ID or a URL |
| verifier\_issuer | Issuer for the verifier | Can be an ID or a URL |
| verifier\_subject | Subject for the verifier | Can be an ID or a URL |