Skip to main content

We’re using the new Federated Search API (beta) and loving it! 

We’re also currently a private community, so content access isn’t an issue. However, we’re exploring a move to a public community with specific categories, modules, etc permissions set to private (toggled off unregistered/logged-out users). 

In a public community setting, how will the federated search content work for logged-out users? My assumption is that those results will default to the community setting and be public. So when an unregistered user leverages the search bar, they’ll be able to see those listings. 

cc: @Marion Frecaut 

Hello @DannyPancratz. 

In the situation you are describing where your community is public and the content you are federating  is accessible only to registered users the following would happen: Logged out users will see the federated content in the search result (the title  in the live search dropdown and the title and a small description in the search result page). However when they click on a result they will be redirected to a log in screen on whatever tool the federated content is coming from.

Let me know if that is answering your question

Thanks, Marion! That’s a good, workable solution! Another reason to love that search API!

@DannyPancratz I’ve got a similar issue and I resorted to some custom code to show a tooltip when hovering on sources in the search page. The script also blocks people from selecting other sources than community and preselected the community source, all this just for a certain custom role which is default on our community. Of course it does not solve the issue of the search result preview, but these show external link icons on federated search items so on our side people expect that there might be a login/ restriction, so we can live with it. Let me know if you’re interested I can share!

Thanks, @SmartlyGreg. I’ll keep that in mind as an addition way to lock things down. 

Reply


Terms & ConditionsCookie settings