IBM Support

Restricting access to attachments on a FTP server when using IBM Rational ClearQuest Attachments 2.x Package

Question & Answer


How can I control access to ClearQuest Attachments 2.x attachment files when they are stored on an FTP server?


Using IBM Rational ClearQuest Attachments 2.x package, you can store files attached to a ClearQuest record on an FTP server. A ClearQuest user can access attachments through links provided on the ClearQuest records that have an attachment. Users also see the full path to the attachment and can use it to browse the FTP server. They may also have permission to delete files or directories, or add files and directories, or rename files and directories. This browsing and modification capability of the FTP server is a function of your FTP server, which you may not want to allow.


To control access to your FTP server, such that ClearQuest users can only retrieve the attachments, you need to configure and set up your FTP server to impose access restriction. To achieve this restriction level and yet allow the ClearQuest Attachments package to work properly, configure your FTP server to allow full access to the account holder of the ClearQuest Attachments 2.x package -- the account you used in the record-type AXPAttachmentControl when setting up ClearQuest Attachments -- and limit other users to read-only access.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.2;;;;;;;;;;;;;8.0;;;;;;;;;8.0.1;","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018