skip to Main Content

Securing attachments in Maximo

So you have secured your Maximo installation using SSL, perhaps by following one of the secure articles in our A3J Blog, and are feeling pretty comfortable that your users are protected. Just as you are about ready to lean back in your chair and enjoy the fruits of your labor you receive an urgent communication with a screenshot showing a Maximo attachment being served up with the unsecured HTTP rather than HTTPS. Sound familiar? Thankfully you will be back to your feeling of tranquility in no time as this fix is a piece of cake.

*Note you could have been prevented the above scenario from occurring by not binding Maximo to an unsecure port. This would not have allowed the attachment to work but would have prevented an unsecure connection.

This Post Has 0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top
×Close search
Search