Canvas SSO Issue



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:



I will have a look to this also.


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.



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?



Hi @jtuckerman,

here are the various files:




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




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

(last 2 entries).



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



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/



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.



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:



That error looks like this



Hi Jack,
I’m running into exactly the same console message as you can see in the screenshot from Feb 19:
“No Access-Control-Allow-Origin …”

This happens since a major Windows upgrade (Windows-1709 Upgrade) which is currently rolled out in our company. On my own computer, which has not been updated yet, this error does not occur and Canvas just logs me in. But I’ve seen this issue now on two different computers that already received the update. I did not change anything in Canvas or TM1 configuration, but suddenly this error comes up.

Has anyone similar experiences after 1709 Windows update?

Any suggestion very welcome.


Hi @andreas.franke,

To further isolate the issue, can you check which URL on the console is this error occurring for? After that, compare it with the SSO URL in the header.script.init.ftl file. Note that the base URL has to be exactly the same, i.e. if the server is accessed via http://cognos01, then the url in the FTL file should have like http://cognos01 and not http://cognos01:80 .

The other area to check possibly is if the xdomain.canvas.html/js file in the Cognos BI server is accessible from the user’s PC. It might have been a security update prevents access for them. You can try to test this out from the browser and type http://cognos01/xdomain.canvas.html for example.




Hi Paul,

the following console log occurs when I try to log in from a computer that already was updated:

Here are the relevant Canvas/BI configuration files:

I can confirm that both xdomain.canvas.js and xdomain.canvas.html are accessible from the web browser via:

I restarted all servers involved and the complete Windows servers this morning to get rid of any problem that might occur due to a pending reboot on server side, but issue remained.

Any idea how to move on from here?

Thanks a lot,


Hi @andreas.franke,

How about the content of the header.script.init.ftl file? Also, what is the URL that you are using to access your Canvas?

The error seems to be connected to accessing the Canvas server first. Is it behind a load balancer or are you accessing it directly?



Hi Paul,

sorry I missed that one, see contents below:

The URL is:

I connect directly.

In parallel I opened a ticket for our internal IT service provider to check what else might have changed (policies e.g.) that might prevent the cross-site request. But I do not expect any useful answer from that request. Do you have a chance to test a similar setup on a Windows 10 computer using Edge and the 1709 update installed.



Hi @andreas.franke,

Another area we could check is via browsers:

Can you try it with Chrome? Looking at the error screenshot, I would assume that it was IE/Edge.

Then another area we could check is if Cognos BI is able to redirect to Canvas. From your browser, look out under Network tab, that URL that reads has the cognos/cgi-bin in its path. This is a long URL, so once you find it, copy and paste that into the browser address bar and press enter.

Does the above redirect you into your Canvas application with a CAMPassport into the URL now?



Hi Paul,

I just installed Chrome on the updated workstation and will continue debugging with this one instead of Edge. Error looks the same, although somewhat more detailed:

Remark: I had to switch to a different Canvas application (ODC instead of AIMS) because I had to switch off single sign on for the AIMS application in order to provide a workaround for the users. Besides that, error message and sympton (no login) is the same, so let’s continue with this one.

The redirection URL that I found in the network tab is the following:

I copied it into a new browser tab and hit enter.

It first redirects me to the following URL:

Then after a few seconds, it again redirects me to:

That is strange, as it redirects me to another Canvas site within the same application (“cashflowkpi”). Not sure where this 2nd redirect is coming from. However, the page still won’t log me in, again resulting in the same error I came up with initially:

However, coming back to your question: yes, it redirects me to my Canvas application with a CAMPasswort in the URL.



Hi @andreas.franke,

Thanks for those details! It is great that the URL has redirected to Canvas with the CAMPassport.

Please contact your local Cubewise office so that they can create a ticket for the issue that you are experiencing.