OpenAPITools / OpenAPITools/openapi-generator
[REQ][Slim4] Add OAuth2 server library
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
After spending too much time with own custom OAuth2 server implementations I've tried to find something recommended by framework authors. Here is list of server libraries(source Server Libraries):
- PHP OAuth2 Server and Demo
- PHP OAuth 2.0 Auth and Resource Server and Demo
- PHP OAuth2.0 for Silex and Demo
- PHP OAuth2.0 for Symfony and Demo
- Nette OAuth2 provider for Nette framework and Nette REST API bundle
Describe the solution you'd like
I'm going to add auth library from list above to PHP Slim server generator. I'm not sure which one yet, so feel free to suggest. I've already checked PHP OAuth2 Server and not satisfied, repo looks pretty outdated, there are many open issues and PRs. The most weird think is that author stores sha1 encrypted passwords in database by default instead of use of password_hash PHP builtin function.
Ref to described function:
https://github.com/bshaffer/oauth2-server-php/blob/5a0c8000d4763b276919e2106f54eddda6bc50fa/src/OAuth2/Storage/Pdo.php#L437-L441
Additional context
If you have any experience with library from list above, please describe it. Keep in mind that PHP Slim Framework is very tiny and doesn't have hundreds of builtin helpers/utilities like Symfony has.
cc @jebentier @dkarlovi @mandrean @jfastnacht @ackintosh @renepardon
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the PHP Slim server generator and comparing the OAuth2 server libraries listed in the issue, including the referenced OAuth2/Storage/Pdo.php implementation. Define which library and integration scope are acceptable before work begins; done means the selected library is integrated into generated Slim server output with documented usage and verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100