cakephp-swagger-bake VS OAuth 2.0 Client

I do work in that space. I build APIs and I use them. I built a springdoc for php so I know a bit about what I am talking about: https://github.com/cnizzardini/cakephp-swagger-bake

The Postman UX is not good on it. It's easy to get lost in tabs, they should ditch the tabs and categorize requests under the actual endpoint. There is also no way to easily save like requests and give them better names that is also searchable. It's also built on electron which means its slow and clunky.

There is nothing good in this space. Swagger would do it if they let you save requests to local browser storage and just added a history dropdown to the endpoints. I use swagger and save common requests to a file system and open them in sublime. if its just JSON payloads I am working with it does the job.

This https://github.com/cnizzardini/cakephp-swagger-bake and this https://mixerapi.com have been the result of my work.

This can easily integrate into your existing github actions, here is an example of its usage on a project I maintain: https://github.com/cnizzardini/cakephp-swagger-bake

https://github.com/cnizzardini/cakephp-swagger-bake which builds out openapi from your cakephp applications meta data. One of many projects I took up to occupy myself during covid lockdowns.

Really anything modern works. I thought Laravel was supposed to be easy to learn, but I have only poked around. Symfony is fine, I've done a lot in it. I've used CakePHP a ton and as a shameless promotion I built this OpenAPI/Swagger/Redoc generator for it: https://github.com/cnizzardini/cakephp-swagger-bake/ and if my side project was further a long I'd of course recommend: https://mixerapi.com buts its still alpha.

League/oauth2-client has a lot of implementations

Have a look on this one https://oauth2-client.thephpleague.com/

In regards to oauth the phpleague packages are fairly popular. Again, the flow requires some redirect dancing so not something that can be (simply) just a single boolean-returning method on the PHP side. Additionally, oauth is a relatively weak standard (Especially where you want to verify identity) in which case platform specific actions/tweaks are needed hence why most use platform-specific oauth libraries. OIDC builds upon oauth to standardize the flow, including getting the identity, but it isn't supported by all platforms offering oauth.

For the client side, I'll be using the library league/oauth2-client.

"Login with Google/Facebook/Twitter/etc": That's called OAuth2 and quite easy to implement. This package is good OAuth2 client to start.

I'd recommend using a library - for Azure AD OAuth we've been using https://github.com/thephpleague/oauth2-client + https://github.com/thenetworg/oauth2-azure (see also https://oauth2-client.thephpleague.com/providers/thirdparty/ )

For Azure AD, I'd recommend the combination of https://github.com/thephpleague/oauth2-client for the authentication part (getting the token) and the Microsoft Graph SDK for then using the token to get information about the user https://github.com/microsoftgraph/msgraph-sdk-php

Here's a good example of that: https://github.com/thephpleague/oauth2-client/blob/master/.gitattributes