Maximo Open Forum

 View Only

 DOCLINKS

Jump to  Best Answer
  • Everything Maximo
  • Integrations
  • Maximo Application Suite
Appu nair's profile image
Appu nair posted 11-03-2025 17:20

We are running a SNO cluster with doclinks pointing to /doclinks NFS PVC.All of that is working fine and when at the pod terminal I can see the file I added sitting there.I also configured the relevant system properties and in Assets I added a file and it created the file in the pod

I have configured in Assets the manage Library Folders thus

/doclinks=https://demo.manage.demo.apps.sno-cluster.*************/doclinks however on retreival I get a liberty webserver error .If I do the mxe.doclink.securedAttachment and mxe.doclink.securedAttachmentDebug true then the file is served but we really want the non secure meaning the https server serving the document wondering if anyone knows what to do

URL executed https://demo.manage.demo.apps.sno-cluster.**************/doclinks/Attachments/MAS9Doclinks.docx our domain masked

Appu 11-042025

As Per  @Steven Shull I tested the queries using Postman and was able to download a Doclinks object in the secure method, so we will end up retrofitting our product to support that 

Steven Shull's profile image
Steven Shull  Best Answer

Maximo does not support insecure attachments in MAS. There is no web server (such as IBM HTTP Server) to serve those attachments. You'd need to customize Maximo to do something like this. For example, you can create your own API route with a custom java class and say that it is before authentication to serve those attachments without requiring credentials similar to how IBM HTTP Server would normally behave. Your URL would be different (/maximo/api/doclinks for example) but it should be doable.

But I would strongly advise against exposing attachments without authentication. Even if you have no plans to ever run in a cloud environment, you can never use the attachment functionality for anything even remotely sensitive (POs, sensitive information on assets like IP addresses, etc.) because anyone can access the file. Maximo restricting you to attachments you have visibility to see is a critical security feature. 

If this is to support some specific use case (IE you have logos in attachments that you want to show in a BIRT report easier, though you can use the REST API to display secure attachments), I would try and move that specific use case out of attachments into an external repository and use URL links instead.