Libraries tagged by line oauth
brianrlewis/magic-admin
35 Downloads
Unofficial implementation of Magic Admin SDK specification
vanguardkras/simplegoogleauth
9 Downloads
Small package to easily generate google auth link and retrieve users' information (email, name, etc).
stepthefkup/easy-identity
264 Downloads
Tools to handle authentication like a pro
loyaltycorp/easy-identity
137 Downloads
Tools to handle authentication like a pro
eonx-com/easy-identity
9308 Downloads
Tools to handle authentication like a pro
namelesscoder/cms-fluid
1 Downloads
Fluid is a next-generation templating engine which makes the life of extension authors a lot easier!
bisonlab/common-bundle
762 Downloads
This bundle includes some of the typical stuff the author needs for his projects, like a user object, generic REST stuff and the context system.
redpilllinpro/common-bundle
70 Downloads
This bundle includes some of the typical stuff the author needs for his projects, like a user object, generic REST stuff and the context system.
friartuck6000/wp-parsedown
302 Downloads
Disable the WYSIWYG editor and author content in Markdown, with a live preview
erwinnerwin/laravel-api-generator
12 Downloads
Laravel API Generator is a tool that generates a RESTful API backend for Laravel applications. It helps developers create a complete and functional API in minutes, saving time and streamlining the development process. With features like code generation, customizable templates, and secure authentication, the Laravel API Generator simplifies the creation of robust, scalable, and secure APIs.
myzero1/yii-permission
1 Downloads
An authorization library that supports access control models like RBAC in Yii.it is based on casbin.
fwrepae/fwrepae
0 Downloads
The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.
easyswoole-tool/hyperf-orm-permission
118 Downloads
An authorization library that supports access control models like ACL, RBAC, ABAC in EsaySwoole Hyperf Orm.
casbin/phalcon-permission
0 Downloads
An authorization library that supports access control models like ACL, RBAC, ABAC in Phalcon.
apimaticsupport/conversationsapi
37 Downloads
## Introduction Send messages using unifonic’s Conversations API. Message your target audience over social channels (WhatsApp for Business, Messenger, SMS, etc..). Unifonic conversations API Restful and HTTP **API's** uses The basic Authentication protocol. All request and response bodies are formatted in JSON. ## Get an account To start using the API you need to send an email [email protected] to create an account for you. ## Base URL All URLs referenced in the documentation have the following base: **apis.unifonic.com** ## Security To ensure privacy, we recommend you to use HTTPS for all unifonic API requests. ## Formats conversations API only supports JSON format. All requests must use the Content-type header set to application/json. ## Support We’re here to help! Get in touch with support at and we’ll get back to you as soon as we can or you can contact us throw live chat on our [website] (www.unifonic.com).