You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Adam Pippin f0c28e9e27 Final updates 5 months ago
.phan Resolve all issues identified by phan 6 months ago
config code formatter 6 months ago
database/migrations Move away from storing token + id data on user, use separate token 6 months ago
docs Final updates 5 months ago
examples/custom code formatter 6 months ago
routes commit before some refactoring to basically just make authkit2 the 10 months ago
src Final updates 5 months ago
.editorconfig commit before some refactoring to basically just make authkit2 the 10 months ago
.gitignore Add example of a custom integration 6 months ago
.php_cs.dist code formatter 6 months ago
README.md Final updates 5 months ago
TODO.md Documentation updates 6 months ago
composer.json Resolve all issues identified by phan 6 months ago
composer.lock commit before some refactoring to basically just make authkit2 the 10 months ago

README.md

authkit2

Drop-in OIDC single-sign-on solution for PHP and Laravel projects.

Purpose

Provide a low-impact way to integrate new and existing Laravel projects with a single-sign-on solution providing identities for users and software across an entire ecosystem of projects.

Features

  • Drop-in, almost zero-config solution.
  • Integrates with existing Laravel user and authentication systems.
  • Exposes core functionality in a framework-agnostic way to allow use outside of Laravel.

Getting Started

These documents generally reference Keycloak as the OpenID Connect (OIDC) provider, however it should ostensibly work with any provider.

Laravel

Generic

Other Documentation

Contributing

Before submitting a PR, please run phan across your branch and ensure that no issues are reported:

$ composer analyze

If any issues are returned, please resolve the underlying issue(s). Do not just twist your code into a knot trying to work around the analysis. Any use of the suppression comments to suppress issues require a comment immediately preceeding explaining in detail why the code is provably correct. However, if there is any workaround besides disabling issue reporting the change will be sent back for further refinement.

After analysis, please ensure your changes follow the code formatting standards used in this project by running php-cs-fixer:

$ composer format