This plugin contains the {secure-include} macro, allowing view access from one space into another space with different security permissions.
This macro will eventually contain several security-related services, but initially {secure-include} is the only macro provided. See the macro description below for details.
This macro does potentially allow view access into pages which would otherwise be inaccessible. However, it does not allow any access which would not be possible by someone who could view the inaccessible page simply copying and pasting the page contents into another space. That is, if you trust people to view a page in a restricted space, then this does not give them any further power.
To view the macro's documentation, click on its name below.
Has anyone else seen issues with images in securely included pages? I noted it as a bug but figured I might get more discussion if I posted a comment here.
Images attached to the page being included now display correctly (as of 1.0-dr4), as well as attachments. Links to other secured pages or images will not work, however.
Thankyou thankyou thankyou!!!! Exactly what I needed
Like you I am strongly a single-source person. Cut and paste is a maintenance nightmare but I need security in this case too.
Actually I would desire the option to include PART of another page etc - I have a master page with User level information followed by internal information - all on one page is good for approved viewers, but I'd love to secure-include just a marked section onto a public page - or achieve this effect in some way. Also oneday secureinlcuding just some metadata etc.
It may be possible to have a {secure-zone} type macro, where the page editor gets a one-off chance to enter in a macro body which may include metadata or whatever. I won't have time to get that built any time soon, probably.
However, in the meantime, a way about it might be to have a sub-page which only contains the specific part you want to share, and then have your main page in the secure space include the sub-page using the {include} macro. That way, it's just the smaller section which is shared between the two spaces, but you still have the effect of the full page in the secure space.
Makes perfect sense, indeed that is exactly the solution I came up with and am using. Works quite well. The only "catch" in my case is that we then end up with pages for item A something like "A Overview" and "A Detail" where "A Detail" does an {include:A Overview}.
Now I am a demanding creature and I have a page higher up in a public hierarchy that lists all the items A, B, C etc that one might want to view. If one is not sufficient approved (eg anonymous/groups) then I need to link to "A Overview" but if one is approved then I need to link to "A Detail".
This requires about 10 lines along the lines of (syntax from memory - I'm still new to this)
This is doable but awkward for 100 items.
I should learn how to write these things (I'm more a C/C++/Python/Perl person than a Java person) and then I could create either an
OR I might just do the secure section include (downloading your source now and perhaps taking ideas from "snippet" macro or multi-include macros)
then again I might just decide my users are not that sophisticated and just hide the "secure" content from display whilst leaving it in the acutal HTML.
As an aside as a newcomer it seems to me the lack of a distinctive macro trailer syntax (ala XML <thing> </thing>) must make parsing harder and nesting impossible....
Has anyone else seen issues with images in securely included pages? I noted it as a bug but figured I might get more discussion if I posted a comment here.
http://jira.nextgencoder.com/browse/PERI-4
Images attached to the page being included now display correctly (as of 1.0-dr4), as well as attachments. Links to other secured pages or images will not work, however.
Thankyou thankyou thankyou!!!! Exactly what I needed
Like you I am strongly a single-source person. Cut and paste is a maintenance nightmare but I need security in this case too.
Actually I would desire the option to include PART of another page etc - I have a master page with User level information followed by internal information - all on one page is good for approved viewers, but I'd love to secure-include just a marked section onto a public page - or achieve this effect in some way. Also oneday secureinlcuding just some metadata etc.
Anyhow many thanks - - Kim
Hi Kim,
It may be possible to have a {secure-zone} type macro, where the page editor gets a one-off chance to enter in a macro body which may include metadata or whatever. I won't have time to get that built any time soon, probably.
However, in the meantime, a way about it might be to have a sub-page which only contains the specific part you want to share, and then have your main page in the secure space include the sub-page using the {include} macro. That way, it's just the smaller section which is shared between the two spaces, but you still have the effect of the full page in the secure space.
Don't know if that made any sense...
Makes perfect sense, indeed that is exactly the solution I came up with and am using. Works quite well. The only "catch" in my case is that we then end up with pages for item A something like "A Overview" and "A Detail" where "A Detail" does an {include:A Overview}.
Now I am a demanding creature and I have a page higher up in a public hierarchy that lists all the items A, B, C etc that one might want to view. If one is not sufficient approved (eg anonymous/groups) then I need to link to "A Overview" but if one is approved then I need to link to "A Detail".
This requires about 10 lines along the lines of (syntax from memory - I'm still new to this)
{show-to|group=confluence-users|link=A Detail}A{show-to} {hide-from|group=confluence-users|link=A Overview}A{hide-from}This is doable but awkward for 100 items.
I should learn how to write these things (I'm more a C/C++/Python/Perl person than a Java person) and then I could create either an
{link-if|CONDITION|link-if=A Overview|link-else=A Detail}A{link-if}OR I might just do the secure section include (downloading your source now and perhaps taking ideas from "snippet" macro or multi-include macros)
then again I might just decide my users are not that sophisticated and just hide the "secure" content from display whilst leaving it in the acutal HTML.
As an aside as a newcomer it seems to me the lack of a distinctive macro trailer syntax (ala XML <thing> </thing>) must make parsing harder and nesting impossible....
best regards
kim