Libraries tagged by crowdentials
piurafunk/docker-php
9 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
phil/paged-media-bundle
2 Downloads
phil/paged-media in Symfony: the native PDF writer and Gotenberg behind one service, Gotenberg's URL, credentials, signing certificate and timestamp authority from the configuration, templates by attribute or by name, and Messenger messages that render, run PDF stages or convert office documents
phil/lti
0 Downloads
LTI 1.3 for PHP, on both sides: the tool and the platform, the OpenID Connect launch with its id_token verified by key set, resource link and Deep Linking 2.0 messages, typed roles and claims, and the LTI Advantage services, Assignment and Grade Services and Names and Role Provisioning, with client_credentials access tokens by JWT assertion
phil/backup
2 Downloads
Database and media backups in plain PHP: SQLite, MySQL, MariaDB and PostgreSQL through their own client tools with credentials kept off the command line, media directories in a tar archive, libsodium encryption by chunks, grandfather-father-son rotation, a restore guard and restore tests
pdo-factory/pdo-factory
34 Downloads
Factory class for creating PDO objects using credentials in external config files
paroga/roundcube-nonce_login
84 Downloads
Plugin to allow login via an nonce, created by an api call, to avoid the sharing of credentials when multiple people use the same account.
ordereazi/commerce-sdk
8 Downloads
Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.
or81/eloquent
13 Downloads
A lightweight, dependency-free ORM and SQL query builder for PHP with a Laravel-style fluent API. Supports MySQL and SQLite, reads its credentials from .env, and queries by Jalali (Shamsi) date out of the box.
onemineral/laravel-secrets-manager
4640 Downloads
Package for managing credentials
omniticket/helloasso
1 Downloads
Omniticket's HelloAsso, under any PHP host: an association's event forms with their tiers, the registrations of an event, and a ticket's QR code checked among them - read only, through HelloAsso's API v5 (OAuth2 client credentials).
omnisign/dossierfacile
1 Downloads
Omnisign DossierFacile: a rental applicant's file - identity, residency, activity, income, tax, guarantors, as the State checked them - shared with the application through DossierFacile Connect (OpenID Connect on DossierFacile's Keycloak): the consent page, the code exchanged and the file read and linked, the file read again with the partner's client credentials, the partner callbacks with their x-api-key checked; the three-month retention carried on the file. For partners under DossierFacile's charter.
omnilang/amazon
1 Downloads
Omnilang's Amazon Translate, under any PHP host and without the AWS SDK: texts translated with formality, the source language detected by "auto", custom terminologies as glossaries, HTML, text and DOCX documents translated at once - every call signed with Signature Version 4, the credentials given by reference, Amazon's limits and data use declared as data.
omnical/caldav
1 Downloads
Omnical's CalDAV (RFC 4791), under any PHP host: the calendars of iCloud, Fastmail, Nextcloud or any sabre/dav server found from the server's address (current-user-principal, calendar-home-set), their events read (recurrences expanded or kept as RRULE data, time zones, attendees) and written (PUT with If-None-Match and If-Match against lost updates, DELETE), and busy time (free-busy-query, or computed from the events where the server does not answer it) - on sabre/xml and sabre/vobject, credentials by reference.
omnibill/chorus-pro
1 Downloads
Omnibill Chorus Pro: invoices to the French public sector through PISTE - a conformant file deposited (deposer/flux), its deposit followed and the invoice's status read (rechercher/fournisseur), the PISTE client credentials and the technical account's cpro-account header.
oluokunkabiru/api-call-logger
3 Downloads
Provider-agnostic Laravel logger for third-party API calls and incoming webhooks: captures request, response, headers, status and latency with automatic redaction of credentials and PII, plus retry, pruning and a built-in dashboard.