Yea, I changed to the below. I also restarted the app service. I am trying to pull a cube view and that does not work either. Seems like a straight forward setup, not sure what I am missing.
<!-- Specify a list of cross domain URL to allow access to TM1Web.
If there are more than one url, each is separated by ",".
Specify "*" to allow any domain to access TM1Web, good for dev and testing.
If not specified, no cross domain access to TM1Web is allowed. -->
<add key="CrossDomainAccessList" value="*" />
<!-- Allows a URL API session to be reused with just an admin host, TM1 server, and (optionally) username -->
<add key="LegacyUrlApiSessionDiscoveryEnabled" value="false" />
we also have a middleware login service that is used for our company apps that is then passed to our cam server. I am removing it form the equation also to see if that might be causing issues.
Well, I tried the “False”, removing the middleware and changing to the path you recommended.
I think my issue is even logging in through web. Whats odd is that its not even prompting for me to log in like other pages do and just giving 404 errors in console.
Request URL:http:///financechet/api/tokens/stageFinance
Request Method:GET
Status Code:404 Not Found
Remote Address:10.15.46.187:8080
Referrer Policy:no-referrer-when-downgrade
I have tried the /tm1web on the end of the tm1WebUri and without it in the instances.json.
Things in <> i purposely removed.
{
“name”:“stageFinance”,
“restUri”:“http://:8000”,
“tm1WebUri”:“http://:9510”,
“applyParenthesisFormatting”:true,
“chartColorScheme”:["#FB6900", “#F63700”, “#004853”, “#007E80”, “#00B9BD”],
“camNamespaces”:[""]
}
Do you mean that you are not even able to login into:
http://<server name>:9510/tm1web
If so, that should be addressed first before anything else.
Then, is your application located at the webapps\ROOT folder or it is on another folder? And is there another server in between that redirects the requests? I noticed that the Request URL is different from the remote URL (port 80 vs 8080).
The above is the reason why I wanted to check on that. From the URL, the tokens api tthat you are trying to access is at port 80 (URL has no port) → http:///financechet/api/tokens/stageFinance
Where as the remote address found was: 10.15.46.187:8080
Then regarding the other items:
What is the URL that you are typing to get into tm1web?
What is the folder name? If it is named “finance” for example, then to check the tokens, it should be: http:///financechet/finance/api/tokens/stageFinance
and returning this when i go to the url.
{“statusCode”:404,“success”:false,“failed”:true,“message”:“No token found for instance - stageFinance”,“error”:{“message”:“No token found for instance - stageFinance”}}
If I go to a page that just has a tm1web component on it, it never asks me to authenticate. It just hits the below message twice and then brings up the error message for the tm1web component.
You can ignore that last update. I am now under the belief it should be working, but the chrome plug in our IT department uses is blocking it. Will work with them on the issue. Thanks for all the help.