"One of the stumbling blocks we have run across is that for accessing PA on the cloud using TM1PY the suggestion is to use a non-interactive account."Having to use non-interactive accounts is a condition / limitation enforced by Planning Analytics for Cloud (PAoC). It is needed to connect ( as in to logon ) to a TM1 instance running within a PAoC environment from outside the PAoC environment using the TM1 REST API. Non-interactive accounts are not related to TM1py.
"What is the license policy for multiple non-interactive accounts?"AFAIR the non-interactive accounts are included in your PAoC subscriptions, and thus do not come at an extra cost. You can request up to 99 non-interactive accounts.
"I would like IBM to answer why we have to use non-interactive accounts and not the regular ones for IBM Cloud?"A PAOC environment is using Cognos Access Manager (CAM) for user authentication. CAM forwards a user logon to an external authentication provider, either to a standard one like LDAP which is mapped / tied to a Cognos namespace or to a custom one, using a Custom Java Authentication provider (CJAP). A CJAP has limitatations.
The IBMid being used for PAoC user authentication is a custom authentication provider, thus using a CJAP. The IBMid is used to logon to a PAoC environment. That is all the CJAP does. The IBMid cannot be used to connect to a TM1 instance running within a PAoC environment using the TM1 REST API.
To achieve that a standard authentication provider must be used. Thus a LDAP Server is connected to a PAoC environment, hosting the non-interactive accounts. This LDAP Server is mapped / tied to the Cognos namespace "LDAP".
------------------------------
Bernd Siebert
------------------------------