Canvas SSO Issue

jtuckerman 2018-01-09 20:01:50 UTC #21

I’m not sure if you’re still having issues with this, but I resolved an SSO issue today that involved steps that are not in the current guide, you may have the same problem:

https://forum.cubewise.com/t/unknown-sso-error/1095

Jack

sschreurs 2018-01-09 20:25:06 UTC #22

Hi
I will have a look to this also.
Thanks

sschreurs 2018-02-19 11:00:33 UTC #23

Hi Al

Back again with another issue with SSO configuration.
After setting up the new server at the customer, I have now as error
"No Access Control Allow Origin" header is present on the requested source.

All requested files seem to be ok. When looking at the console, I’ve got dimensions and batch errors. When SSO is set on false, I can connect but with the same dimensions and batch errors.

jtuckerman 2018-02-19 11:41:29 UTC #24

@sschreurs,

In our experience the “No Access Control Allow Origin” error usually points towards something being incorrectly configured on the BI server, or in the Canvas header.script.init file.

What’s in your Canvas header.script.init file and your variables_TM1.xml file on the BI server?

Jack

sschreurs 2018-02-19 11:51:26 UTC #25

Hi @jtuckerman,

here are the various files:

jtuckerman 2018-02-19 11:53:56 UTC #26

@sschreurs,

I see you’ve got the samples in there, does that work OK (with SSO).

Jack

jtuckerman 2018-02-19 12:00:26 UTC #27

@sschreurs,

I think the problem is that you are missing a final / after your instance names in variables_TM1.

(last 2 entries).

Jack

sschreurs 2018-02-19 13:45:31 UTC #28

I’ve tested this but it doesn’t work with adding a final /

jtuckerman 2018-02-19 13:59:52 UTC #29

@sschreurs

You shouldn’t need the “#” after the canvas port (8080) in your variables_TM1 either.

It should read the same way as the samples URL, i.e. server/port/app/

Jack

plim 2018-02-19 22:18:40 UTC #30

Hi @sschreurs,

How was it? Looking at the configuration, it is highly likely because of the number 80:

YOu do not need the port 80 as by default, http is through port 80. That goes for https (443).

Although they are the same, the browser, specifically through JS still treats them as different domains.

–
Paul

sschreurs 2018-02-20 08:03:13 UTC #31

Hi @plim,

Both proposed solution doesn’t work but by modifying the port 80, I do not have the No Access Control Allow Origin” error anymore:

jtuckerman 2018-02-20 08:35:01 UTC #32

@sschreurs

That error looks like this https://forum.cubewise.com/t/unknown-sso-error/1095/2

Jack