Libraries tagged by credentials

voopite/lumen-keycloak-client

0 Favers
6 Downloads

Simple Keycloak Client Lumen microservices Client Credentials authenticate

Go to Download


user10/raas

0 Favers
24 Downloads

With this RESTful API you can integrate a global reward or incentive program into your app or platform. If you have any questions or if you'd like to receive your own credentials, please contact us at [email protected].

Go to Download


tqtran7/flarum-ext-auth-ibm

1 Favers
11 Downloads

Allow users to log in with IBM credentials.

Go to Download


tangocard/raas

0 Favers
18601 Downloads

With this RESTful API you can integrate a global reward or incentive program into your app or platform. If you have any questions or if you'd like to receive your own credentials, please contact us at [email protected].

Go to Download


ssibtr/laravel-ibm-ibmi

0 Favers
5 Downloads

laravel-ibm-ibmi is a simple DB2 & Toolkit for IBMi service provider for Laravel. It provides DB2 Connection by extending the Illuminate Database component of the laravel framework. Plus it also provides Toolkit for IBMi so that you can access IBMi resources with same credentials.

Go to Download


scheibo/steamsso

0 Favers
5 Downloads

A Steam SSO plugin for seamless integration with Steam accounts in Kirby, enabling users to log in with their Steam credentials. Simplifies authentication for gaming platforms and services.

Go to Download


saaspass/module

2 Favers
7 Downloads

Module that makes it possible to login to Magento with SAASPASS credentials

Go to Download


rocker/google-login

0 Favers
2 Downloads

Package that makes it possible to authenticate against a PHP-Rocker application using google user credentials (https://github.com/victorjonsson/PHP-Rocker)

Go to Download


richpeers/laravel-log-oauth2-curl

1 Favers
1 Downloads

Queue Laravel Logs send via curl and auth via OAuth2 Client Credentials Grant Token

Go to Download


piurafunk/docker-php

0 Favers
8 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..." } ```

Go to Download


pflorek/php-basic-auth

3 Favers
68 Downloads

Provides a simple way to get or set credentials (username, password) on a PSR-7 `RequestInterface`. Also it helps challenging an unauthorized client by adding the 'WWW-authenticate' header line with status code 401 to a PSR-7 `ResponseInterface`.

Go to Download


pdo-factory/pdo-factory

2 Favers
31 Downloads

Factory class for creating PDO objects using credentials in external config files

Go to Download


paroga/roundcube-nonce_login

1 Favers
78 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.

Go to Download


onsigbaar/onsigbaar

2 Favers
56 Downloads

Laravel Passport OAuth2 API Server authentication using Resouce Owner Password Credential Grant with optional Laravel admin dashboard.

Go to Download


onemineral/laravel-secrets-manager

0 Favers
4637 Downloads

Package for managing credentials

Go to Download


<< Previous Next >>