TM1 Forum

Hello Everyone,

I have a quick question, I have embedded the Tm1web url api in my application.

Working in IntegratedSecuritymode 5,

authenticationMode is CAMNamespace

http://fullyqualified-domainname:9510/t ... =localhost

For the every call, tm1web login page comes and without giving any input, click on login redirect to report.

How to avoid tm1web login and redirect to websheet directly.

Do I need to set anything in the tm1web_config.xml?

Thanks
Kavitha

It's been a while since I have used the web URL API, but if memory serves it's just a matter of making sure that you pass in the AdminHost parameter exactly the same way it is specified when the users first log in.
This is usually the way it is defined in the TM1 Web config file - so even if it is all on one server, localhost won't suffice if it is specified in the config file as a FQDN.

Thanks for your reply.

I have specified the below in tm1web_config.html. Is this do you mean?

<!-- When performing CAM authentication, optional redirection url override example http://127.0.0.1:9510/tm1web -->
<add key="ExternalUrl" value="http://FQDN:9510/tm1web" />

In url I specified AdminHost=FQDN while invoking the websheet. Do I need to configure in any other place?

**tm1web runs on different machine, CA runs in diffferent machine.

But for IntegratedSecuritymode=1 its works fine. Problem is only with IntegratedSecuritymode=5

Are you using SSO or are you being prompted for credentials on first connection to TM1Web?
If you're being prompted check out this
https://www.ibm.com/docs/en/planning-an ... es-session

Each new call to TM1Web is treated as a separate session. In order to ensure the user isn't prompted for credentials each time, you can grab the sessiontoken and parse it as part of your URL.

If you have SSO and don't use the sessiontoken, the user will be automatically logged in each time and if a web page for login is still displayed it means the adminhost and servername passed in url isn't correct or SSO isn't working. Depending on your setup for SSO, you may need to use the FQDN as the adminhost.

If the adminhost is already using the FQDN, then check that navigating to TM1Web (without URL API) works with SSO, if it doesn't then the issue is with SSO.