search

ollieread / multiauth

Laravel multi auth
441 stars 109 forks source link

Laravel 5 #86

Closed irman closed 9 years ago

irman commented 9 years ago

This seems like a great package and I regret that haven't found it in my previous projects. With the release of Laravel 5, I started my new projects with it too. It would be great too if you would release the version that supports 5. I know you planned it, but is there any new news? Like how's the progress and such and when you expect to release it? If you've not done anything yet I might find some time at home to do it.

visualcom commented 9 years ago

+1

dulumao commented 9 years ago

+1

wulongqiu commented 9 years ago

+1

jmsaugar commented 9 years ago

+1

dvigueras commented 9 years ago

:+1:

llaski commented 9 years ago

+1

jithujose commented 9 years ago

:+1: :+1:

Dubz commented 9 years ago

+1

Dubz commented 9 years ago

It appears @ollieread already responded to this issue and closed it. https://github.com/ollieread/multiauth/issues/82

I guess its up to another user to do this. I'd volunteer, but I just started using laravel so I wouldn't even know where to begin.

Dubz commented 9 years ago

Check the bottom of this form post on laracsts, maybe it will help some of you. I haven't tried it yet but I'm about to. Perhaps @ollieread can update this git using the information?

https://laracasts.com/discuss/channels/general-discussion/multiple-authentication-in-laravel-5-ldap-and-default-auth

ollieread commented 9 years ago

It's more that I haven't had much time to do this yet as I've been working a lot. I will do when I get chance, but others are welcome to make PRs.

Dubz commented 9 years ago

Well that stinks, I guess I'll have to work around that part of the system I'm creating as best as I can. I think this issue should remain open however so other users trying to figure out why this won't work on laravel 5 can see it. I wouldn't have thought to look in the closed section of the issues area when I first realized it and would have made a duplicate post. I see the closed being a solved/declined rather than a pending/on hold. That's just my opinion.

sboo commented 9 years ago

Check my fork https://github.com/sboo/multiauth and post on laracasts. maybe that helps

https://laracasts.com/discuss/channels/general-discussion/multiple-authentication-in-laravel-5-ldap-and-default-auth/replies/44260

visualcom commented 9 years ago

Hi!

I'm using Laravel 5 native auth to handle multiple auth contexts (database tables)... It's not difficult, please check this Gist:

https://gist.github.com/danielcoimbra/64b779b4d9e522bc3373

Daniel

2015-03-18 22:40 GMT-03:00 Dubz notifications@github.com:

Well that stinks, I guess I'll have to work around that part of the system I'm creating as best as I can. I think this issue should remain open however so other users trying to figure out why this won't work on laravel 5 can see it. I wouldn't have thought to look in the closed section of the issues area when I first realized it and would have made a duplicate post. I see the closed being a solved/declined rather than a pending/on hold. That's just my opinion.

— Reply to this email directly or view it on GitHub https://github.com/ollieread/multiauth/issues/86#issuecomment-83253810.

sahibalejandro commented 9 years ago

@visualcom Changing the value of auth.model is a clever solution, but the session data still the same for both auth contexts, causing when you call Auth::logout() both "sessions" are closed.

This is because Guard::getName() use the same name for the session data no matter what model we are using... :/

It seems we need a more complex solution like @sboo repo.