You are viewing limited content. For full access, please sign in.

Question

Question

LF Cloud Two Public Portals

asked on December 14, 2022

Our customer is implementing SharePoint and some areas are resistant to Laserfiche Cloud because they want all their content centrally accessible in SharePoint. We had an idea to embed the LF Public Portal into SharePoint as an iFrame and after messing with the whitelisting rules in Site Settings, we have it working.

 

The sticking point now is permission related. Some content is to be published externally to the public and here we can use the public portal.

Other content is to be available internally and ideally embedded in SharePoint as described.

The url for the portal references the repository id and we understand LF Cloud only supports one repository?  Is there any way to have two (or more) public portal users with different permission in LF cloud?

It is conceivable there could be a need to publish content to the pubic, to internal staff through an intranet and elected members through an extranet, each with different permissions and access rights.

0 0

Replies

replied on December 14, 2022

I'm not sure this could ever really work. Security requires some kind of authentication or access control, otherwise your "internal" portal view becomes public once someone accidentally emails the url outside your organization. I can't think of a secure approach to this problem that stops short of having users authenticate, at which point you've got the regular web client.

The way you might handle this with a self-hosted solution would be to have a server inside your firewall - it's not ideal from a security standpoint (no access logs, no way to revoke or restrict access), but you at least have some measure of control.

1 0
replied on March 14, 2023

I also have a whole bunch of use cases identical to the one described here.

I agree that the web client handles this better, but things like generating URLs is a lot more complex.

 

0 0
replied on March 14, 2023

Hi Bill, can you expand on what is complex about generating urls for web client vs WebLink? Is it something we could simplify?

0 0
replied on March 15, 2023

Hi Brian -

 

Thanks for the reply. 

It's quite easy in both cases.  I had the Weblink pattern down, but for the Web Client, I was getting hung up on the encoding.  Once I normalized things, there was little difference.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.