Auto-login user from dedicated event instead of tag

[Alexander Obuhovich]

I propose, that we use "u:OnAutoLoginUser" event to perform automatic user login, when needed and don't do such things in "u:TestCodeIsValid" tag.

Using tag in the middle of template results in sidebar being displayed as for non logged-in user, but main page part displayed as for logged-in user (based on "advanced" theme).

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

[Phil]

good idea, so the tag would be used for global page behavior, instead of acting on main content portion only. I'm for it :)

Envoyé avec Sparrow

--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

[Alexander Obuhovich]

Basically tag content will be moved into corresponding event. That's all.

Not sure if we talked about this somewhere, but we actually are missing magic links to a pages, that allows user to auto logged-in, while using them, e.g.

http://www.website.tld/some/page.html?login_token=34534dfsdg453sds

will not only automatically login user based on given token (user, who will be logged-in is pre-generated individually for each user, once needed), but also show /some/page.html, that was requested.

Similar functionality was developer in In-Business task: "#35976 - User Auto-Login on Front-end" for one of Intechnic projects.

[Dmitry Andrejev]

Alex,

By the way, what happens if I open link with Token that suppose to Log me in as User A, but I was already logged in as User B to the same website.

I think I just came across this case.

DA

[Phil]

then you should be logged as User A, as token is a fast login lane, nothing should stop it :)

Envoyé avec Sparrow

To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/7W6rCw0XQrMJ.

[Alexander Obuhovich]

Yes, you will be re-logged-in with user bound to used token. However some residual currently logged-in user session content may stay, like last used order id and such.

Maybe it's better to perform full currently logged-in user (if any) logout procedure (but without redirect) and then attempt to login user associated with given token.

[Dmitry Andrejev]

Agreed Alex,

Would you please make a note of this where needed. I think I saw potential problem on Catalyst project on Approve Order screen.

DA

[Phil]

knowing all problems that could raise, I'd suggest to completely logout B + login A.

Envoyé avec Sparrow