Skip to main content

Updated - Thoughts About Sharing Files Via Link - IBM Connections 6.0 CR4

·575 words·3 mins
Table of Contents

The last IBM Connections 6.0 CR4 introduced the new feature “Sharing Files via Link”. A quite handy way to share files with users by link. Just open the file, go to sharing and select “Share by Link”.

“Share by Link” makes it easy to share and grant read access to personal and Community files.

We tested the feature and it works like a charm, but…​

— What’s New in IBM Connections Cumulative Release 4

  • Everybody who gets this link, can download the shared file (and share the link with others)

  • Even in restricted communities everybody with editor access can create the link

  • The users are not added to the readers field (like mentioned here)

Sharing after downloading with 2 users
  • You don’t see in About > Views who or that anybody downloaded the file
About after downloading with 2 users

So you don’t know if, who or how many users have downloaded your shared file.

On the screenshot you see my testldap user, I tested with this one too, but he has the admin role of all applications, so he can see the file directly in the viewer and he appears in the Viewer list. A user with default access right does not see the Docs Viewer, they only have the option to download the file.

In my eyes that’s nothing I want to have active in my environments. To deactive this feature, go to Gatekeeper (you need to have the admin role in the application Common) and change FILES_ENABLE_FILE_SHARE_WITH_LINK to FALSE.

URL to Gatekeeper: https://yourconnectionsurl.example.com/connections/config/highway.main.gatekeeper.tiles

SnipToolPlusImg

No reboot needed, after a refresh the option for sharing with link has disappeared.

Shared file links generate a “Page Not Found” error message after disabling the feature. If you reenable it, old sharing links are working again.

cnx filenotfound

Changes with Gatekeeper can be tested on the fly. So no reboots or restarts needed. Just try it.

Update 06.03.2019
#

The original post was from 25th of february, but I need to update some things.

Today I checked the functionality again and I think there is only a tiny bit missing to have a working solution, which hopefully can be delivered with an update.

There are differences in the sharing by link, when you share a personal and a community file. It is important if the file can be opened by the IBM Docs Viewer!

So I found several dependencies:

  1. A personal file shared by link which can’t be viewed in the Docs Viewer, can be downloaded by everybody who has the link and the downloading user is not visible in the “Views” Secion of the file.

  2. A personal file which can be opened in the Docs Viewer will create an entry in the “Views” Section!

  3. For community files it is important if the file is viewable in the Docs Viewer and if the user already can access the file (public communities, or users which already are members in the community). I haven’t checked the dependencies with the Docs Viewer in that case. So users which get access to the file through the link (not member, not public shared) are not appearing in the “Views”.

And a really important point:
#

User with editor access in community can only share files by link which they uploaded to the community. Files from owners or other members can’t be shared!

Owners are able to share any file of a community by link.

I’m still not completely happy with the implementation, but I will activate it, when the users can see all downloads and views.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

Use OAuth 2.0 token-based authentication with IBM Connections Mobile App

A lot of people don’t like to store credentials in mobile apps or browsers. A good workaround is the usage of OAuth 2.0 tokens, but the application needs to support it and the server you’re talking to too. The IBM Connections Mobile App can use it for authentication. OAauth2 can be used directly with WebSphere Application Server and Connections 6.0. There are no special OAuth servers or applications needed! The Documentation at IBM was a little bit confusing for me, there are lots of sidenotes, but you just need to do following steps, to use OAuth 2.0 token-based authentication with the IBM Connections Mobile App.

Always have a look at the LDAP

·584 words·3 mins
Today I learned a new lesson during troubleshooting a IBM Connections System. I updated to 6.0 CR2, updated WebSphere to FP13, last fixpack for Docs and so on. You will ask if I added IFP88438 to the list, be sure that I installed this fix which reanables the root element in Federated Repositories. Have a look at WAS 8.5.5 FP12 breaks Domino “root” base entry setting for more details. Then one of the two deployments showed strange behavior with Activities. On the Activitystream I only got an orange error symbol instead of the Todo list and when I opened Activities directly I got an empty page.