This object is in archive! 
Upvote 1

When using SSO the login should be forced before the user is allowed to type in his new Response or

Archived Stebi 10 years ago

When using SSO a user loses the Response or comment he entered because of the redirect to the login page. He gets a warning that the browser wants to leave the page and his input is lost, but he doesn't know why this is the case.

When SSO is active, it shouldn't be possible to enter the text for a comment or new Response before the user has logged in.

Best Answer
photo

In 2.3.5 we've made required actions before posting comment or new topic if you have SSO and/or anonymous topics. So user is prompt to login before adding topic. More in release notes.

kHcIZpAAu9goh8Zbs5a3

Replies (9)

photo
1

Stebi,

We've thought a lot on implementing smooth way of adding responses/comments when SSO only method is switched on, but as of now it shows the message in alert that you are leaving page and all information is lost, because user goes to external login form before submitting the form.

The option to not allow adding comment or response won't work as admin can switch on adding anonymous responses and with switched on anonymous and SSO, they won't get on the form.

Do you have another delicate approach on how it should work in case you have only SSO method enabled?

photo
1

The only thing that comes to mind is to load the SSO page in a popup iframe, so the user doesn't have to leave the page and his text isn't lost. After login the javascript from useresponse is loaded which should be able to access the parent document (no cross domain problems since they have the same origin) to trigger any necessary actions. I haven't tried something like this yet, but it should.

photo
1

Or another possibility is to save the text in the users session and restoring the page and content after the redirect from the login. This should be quite easy I think. When consuming the SSO cookie, useresponse could also check if the session contains any response or comment which should be postet.


The disadvantage of this is that during the login process the user doesn't see his text anymore and may assume that everything is lost, so he closes his browser.

photo
1

Our best approach after discussion is placing alert window that will advice to login if you put focus in title or description or comment field in case you are not logged in and option of only SSO login is switched on?


Thoughts?

photo
1

That could work.

Maybe something like this: The user clicks in the title or comment field and a message pops up saying something like: "To proceed you need to login first. Do you want to do this now?" If he clicks yes he will be redirected to the login page, if no, the page stays.

It would be really cool if after logging in he would be redirected to the page he just left. So that he don't have to search for the topic in which he wanted to post a comment. Currently you are always redirected to the main page after sso login.

photo
1

In 2.3.5 we've made required actions before posting comment or new topic if you have SSO and/or anonymous topics. So user is prompt to login before adding topic. More in release notes.

kHcIZpAAu9goh8Zbs5a3

photo
1

I just installed 2.3.6. The current solution should work well I think.

But there is still one quirk left: When clicking at "New Response" I'm redirected to the page /response/add where I find the login button instead of the input form. When I click the login button I get a warning from the browser if I really want to leave the page and that all content is lost when doing so.

This message should't be displayed, there is no reason to (there is nothing which can be lost) and the users won't know what to do with this type of message.

When I need to login to add a comment it works fine, no warning message appears before redirecting.

photo
1

Identified along other minor nuances. Will fix it by providing patch during next few days

photo
1

Stebi,

Minor bugs in SSO are fixed in 2.3.7 that can be downloaded on Licenses page or via Auto-Upgrade tool.

Replies have been locked on this page!