How to remove all meta information? e.g. used version

As a part of our planned security chain, we would like to remove all possible meta information for all used Atlassian products.

This mean that it will not be enough to "hide" the (footer) information about the used product version by using css. In case of the version is part of the head of each webpage this tag has to be removed also. 

Know somebody a best practice to remove all these information?

I already read the confluence pages with "how to change the footer". But an update- proof solution will be more helpful. 

 

King regards

Andreas

3 answers

1 accepted

This widget could not be displayed.
Justin Koke Atlassian Team Apr 16, 2015

If you did this you would be breaking item 12 (f) of the customer license agreement that you agreed too when you downloaded your Atlassian products:

https://www.atlassian.com/end-user-agreement/

I am not a lawyer, but seems an overkill to not be able to change decorators. Even without source code atlassian gives the way to do it and without changing any jar, vmd, vm or atlassian-owned files.

I do not want to remove the "Powered by Atlassian" mentiond in 6.4 of the user agreement. Just information like the version, which i'm allowed to modify within the footer - that is not recommented by Atlassian for support aspects but it seams to be allowed. See: https://confluence.atlassian.com/x/O4W9CQ

This widget could not be displayed.

Not sure what you want to achieve, but as far as i understand you need to override the vmd files. Something like

<layout class="com.atlassian.confluence.themes.VelocityDecorator" 

            key="main" name="Main Decorator" 

            overrides="/decorators/main.vmd">

        <resource location="/layouts/decorators/main.vmd" name="decorator" type="velocity"/>

    </layout>

would override the atlassian's main.vmd with your /layouts/decorators/main.vmd enabling you to choose what to render and what not. For more decorators look at $CONFLUENCE_INSTALLATION/confluence/decorators

Thanks for your answer. But overwriting an velocity template seams not be the best practice I'm looking for :(

Davin Studer Community Champion Apr 16, 2015

I'm not sure you have a choice. Going to the velocity decorators would be the place to go to remove those things. However, I don't think you are ever going to achieve all of what you want. One big reason is that even if you manage to get rid of the stuff that is hard-coded on the pages the AJS library will dynamically put stuff into the page after it has come down to the client. Which mean if you wanted to stop it from doing that you would have to start mucking with their AJS framework.

This widget could not be displayed.

Finally i've created a suggestion. For someone who's interested: https://jira.atlassian.com/browse/JRA-43726

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

573 views 25 15
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you