<QC/ALM Support Tip> How to restrict access to the OTA API in ALM 11.x and above
http://<server_name>:<port>/qcbin/start_a.jsp . Please note that you should not use “http:// <server_name>:<port>/qcbin/start_a.jsp?common=true ” as this will register the client.
Is there any discussion on making the OTA access selectable as part of the users role within a project? AT least the ability to restrict the TDAdmin OTA functions would be helpful
1) Users do not have admin rights to their work computers
2) QC cannot be accessed from non-work computers
a) Personal computers cannot have access to QC
b) Consultants cannot use their own computers
3) QTP, etc. cannot be used
In our use, ideally anyone would be able to run OTA scripts (we have a lot of useful extracts, etc.), but only certain users would be able to write scripts. I don't have the slightest idea how/if you would do that, but that's what I would like. Currently, we are relying on people not understanding how to write an OTA script, or knowing that there is such a thing, so not bothering to try. I think that most people think our reports are magic. 🙂
Unfortunately right now there is no way to disable entirely the OTA API in HP ALM.
However there is an ER already logged for this. You can track its status on the following URL:
You can disable the access partially with the following site configuration parameter:
If this parameter is set to “Y” (default), only users belonging to the TDAdmin group can use the OTA Command object.
More information about this parameter can be found here: http://support.openview.hp.com/selfsolve/document/KM00590512