Hi,

We've got a solution where PSM web is framed into our clients corporate website which works perfectly in Firefox, but in internet explorer it keeps asking the user to log in, repeatedly.

So when the frame first loads the PSM content it understandably asks you to login, but then when you click on Order Manager for example, it jumps back to the login screen. It does that for every page.

Any reason why it would do that?

Regards,
Jacques

Please keep in mind that we don't want to 'integrate' the authentication details with the iframe, the user should login as per usual, the only difference being that the application is framed into another site.

I've also removed our customization efforts (JavaScript) and that makes no difference.

The behavior is the same in IE 7 and 8

Anyone home?

Hi Jacques,

Have you tried to clear the cache and cookies for IE?

And you can confirm that this works well with Firefox correct?

This might be something our developers will need to look into.

Let me know the results of clearing the cache and cookies for IE.

You might also want to disable protected mode and try again.

Let me know.

Also please be aware that if you need immediate help I would suggest opening up a support call.

Either by the web: 4hr Maximum contact time.

http://www.objectiflune.com/OL/en-US/Services/Support/ReportIssue/PrintShopMailSuite.aspx

Or phone: 1-866-348-5863 -2hr Maximum Call back time.

That way we can assign a resource to you and answer you in a timelier fashion.


Thanks,

Marc

Hi Marc,

Thanks for the response. I'll try clearing my cache and so forth and get back to you.

By the way, we're a supplier to your customer... we're developing their website for them. Objectif Lune has made it clear that they cannot help us (support wise). Only the customer can create support calls or call for support. This has been one of the worst basic integration experiences we've had.

Regards,
Jacques

Hi Jacques,

I am sorry you are having a bad experience with our newsgroups, but this is not a support channel. This is a end user community. I might suggest using your customer's account to do an actual support request and have access to our full range of resources to assist you solve your problem. Please note that not a single issue is not taken care of, when dealt with through our support channels, given it is in the support scope.

There are custom implementations that are outside of support scope in regards to PrintShop Web, but we will not be in a position to determine that until we look at it.

Please consider contacting your customer to see if you could access their support credentials.

Best regards,

Olivier

Jacques,

I'd like to point out for a moment that nowhere in our documentation is it ever indicated that we support iframes. Frames don't use the same security context in most browsers (specifically IE), so the issue with cookies is known.

However, it may be possible to make it work. Here's a reference page that may help you in resolving this issue (which doesn't actually have anything to do with PrintShop Mail Web): http://stackoverflow.com/questions/389456/cookie-blocked-not-saved-in-iframe-in-internet-explorer

Hi Oliver,

My problem is only partly with the support forums in that the responses to date have been quite slow.

The only reason we went to these forums is because Objectif Lune in South Africa won't help us, only our mutual client, which is the most bizarre thing considering this client is relying on us to help them with technical questions that they aren't meant to understand.

Back to the problem with IE.

To confirm:
1. I've cleared cache and cookies, didn't change anything
2. It works fine in Firefox 6, Safari 4, Chrome 11
3. I'm testing on Windows XP and as far as I know protected mode was only available starting from Vista, but I did a quick check and there doesn't seem to be anything like Protected Mode enabled.

Regards,
Jacques

Jacques,

Did you read the Stack Overflow page I linked to? It does not mention Protected Mode at all and clearly indicates that this is an issue with how IE deals with security inside of an iFrame (and it's a widely known issue). If other browsers deal with it differently it's partly because of a different philosophy; remember that IE is widely used in governmental and financial institutions, so security has to be treated differently in that regards. Chrome, FireFox and Safari are catered towards end-users, for which it's more important to have function than security (up to a certain extent).

Again, what you're trying to do is and unsupported method of doing "integration", which is slapping a website inside an iFrame and hoping it will work. You need to use the methods described in the Web Integration guide if you wish to have a fully functional implementation. Anything else is patching and hacking and leaves the door open to much issues in the future, whether technical, security or legal.

Finally, I'll re-instate the point we've been trying to make about support: You can use our mutual client's credentials (serial number) in order to receive support, with their permission.