My team and I(the business/idea guy) are developing a new Startup using the Laravel framework. I'm not a tech guy but I want to learn as much as possible.
We began with installing and utilizing the Sentry Bundle, and then added the OneAuth bundle for the Facebook login; however, we continued to get errors.
Is OneAuth not compatible with Sentry?
Sentry is coming out with a socialplugin soon. Should we just wait for that or how should we go about this?
OneAuth author here, the problem right now is Sentry is not using Laravel Auth Driver to authenticate the user which make it difficult for the integration to happen. The two way to tackle the limitation:
Convert all Auth called in OneAuth to use Laravel\IoC, this would require Sentry to register IoC on their side.
Sentry to add an adapter class (extends Laravel\Auth\Drivers\Driver)
Either ways, there some works need to be done on Sentry side, I'm open for solution if they are looking to use OneAuth as their social plugin.
Related
Is it possible to connect to Keycloak an Angular 10+ spa, which gives almost the same functionality as Keycloaks Account-Console? Does anyone have experience with this?
New account console looks like "just an openid-connect"-ed reactjs webapp, i think.
Or am I better if I give up on this, and thinking in the theme functionality of account-console?
New account console is shipped also with new account API (!= admin REST API), so nothing stopping you to build own independent SPA (in your favorite platform: Angular, React, Vue, ...), which will utilize that account API.
See (random) blog post about that: https://www.marcus-povey.co.uk/2020/10/12/using-the-keycloak-accounts-management-api/
I have a Laravel project with a passport api. I want my other websites to connect to this same authentification. In the future, even ios and android apps can authentify too. How can i set my other laravel projets to use this api oauth? Can i guard my pages with it?
Before doing anything i want to know if this is possible or if there is a better idea of doing this.
Short answer: Yes, this is possible!
Long answer:
Passport provides OAuth2 which is the very same authentication protocol used by Sign in with Facebook and sing in with GitHub etc.
So your app with Passport is the user provider and your other apps are consumers. In the case of the consumers any OAuth2 client will do the trick (as long as you can create a custom provider for your Passport "server" app).
Laravel got your back with that too with: https://laravel.com/docs/5.8/socialite. You can create a custom provider for your Passport "server" app.
TL;DR: Just like you would implement "Sign in with GitHub" (if you did that before) you can implement "Sign in with my Passport app" by writing your custom OAuth2 provider.
I cannot show much code since this will be highly specific but I do hope my story helps you find the correct packages/articles on how exactly to do this for your use case!
I'm trying to build an internal admin system to get to grips with creating a Laravel app from scratch. Currently everything is public so I'm looking at implementing a very simple login system.
There will be no DB connection needed as we want a single user. We'll store the relevant username and password in the .env file most likely.
I feel like I've looked everywhere and haven't been able to find any tutorials covering this requirement! From everything I've read it seems I have to use a 'custom authentication driver' or possibly build my own user provider class but I have no idea how to go about this task.
The idea is that if the app is expanded in future we'd like to be able to just go back to using Laravel's built in db auth functionality. For this reason it would be nice to retain all the common methods relating to checking the current user, using auth middleware on my routes and managing login tokens etc.
Thanks in advance for any help offered.
With the new Codeigniter 3.0 version what authentication libraries do you use?
Flexi auth was very good and robust with great documentation for CI 2.0 but it is old and as I can see it is discontinued. Of course it does not work out of the box with CI 3.0. I have tested it and tried to migrate it to CI 3.0 but as it uses the old ci_sessions schema I have seen that it has a lot work to be made to rewrite all the code parts that use sessions. It seems to work with file sessions and some alterations on its code though.
Community auth has a CI 3.0 version but as I have seen, it has many bugs and it is nowhere near reliable at this time. I have tested it thoroughly and it cannot work properly as it has problems with its token jar system and its cookie management. Users cannot login most of the times and it is being used as a whole third-party library at Codeigniter, which personally I don't like as it has a lot of files/folders that are time consuming to be maintained. I would prefer simple CI libraries with 1-2 models like flexi-auth. Although, I wouldn't mind Community Auth's approach if it worked properly.
Tank Auth was a reliable solution in the past but not with Codeigniter 3.0 as it has many incompatibilities too. Questions about its compatibility with CI 3.0 were asked but no airplanes in the horizon so far.
DX Auth is an old authentication library and as I can see on its github repository, there are some attempts to migrate it on CI 3.0 but I haven't been able personally to test any of them.
So, has anyone successfully integrated (or migrated) any of the previous mentioned libraries on large CI 3.0 web applications? Did you write your own? Did you stick with CI 2 until further CI 3.0 development for that matter?
Update for the down votes
This post about Authentication libraries in codeigniter was very popular and helpful. I believe that posts that help the community in that way should not be closed at least not before some helpful answers. It is not discussed anywhere before and I would really like to see the opinions of more experienced developers for that.
don't let the down votes get ya down.
check out Ion Auth
https://github.com/benedmunds/CodeIgniter-Ion-Auth
take a look at the read me, you will have to rename two files for codeigniter 3. otherwise you can see that there are recent changes to the lib. the author Ben Edmunds is one of the four developers on the new codeigniter council. http://www.codeigniter.com/help/about
Please check Dnato System Login Its Simple, Fast and Lightweight auth codeigniter.
Feature:
-Add user
-Delete user
-Ban, Unban user
-Register new user sent to email token
-Forget password
-Role user level
-Edit user profile
-Gravatar user profile
-Recaptcha by Google
-And much more
Frontend
With Bootstrap Framework.
For a simple library, I use https://github.com/trafficinc/CodeIgniter-Authit (Authit). It is very simple so I can do a lot of customizations to it or just leave it be.
check this library.that is so nice.and with many features
login / logout
Login DDoS Protection
register and signup via email. (send verification code to your email)
users can send private message to other users
user group
create permissions and access control
error in other language
this library for CI2. but if you search about this, you can find lib for CI3
http://codeigniter-aauth-test.readthedocs.io
I'm trying to implement sessions in my sailsjs app. To make login I'm using passport and passport-local, by default passport manage session with serialize and deserialize but how it works, in the documentation talks about use express sessions too. My question is why I maybe have to use both, and how each it works?
This is to learn when use them.
Thanks
Some examples for Sails/Passport/Passport-local integration:
https://gist.github.com/adityamukho/6260759
https://github.com/RelativeMedia/sails-PassportLocalMongoExample
https://github.com/cgmartin/sailsjs-angularjs-bootstrap-example
https://gist.github.com/adityamukho/6260759