SOLVED

User breached permissions via sharing link - Please help!

Iron Contributor

Hi all. I've never EVER seen a SharePoint permission breached unless user error is involved.

 

In this scenario, a user (user1) shared a video via a sharing link 'Specific people only'. One of the recipients (user2) forwarded this to a number of users one of whom (user3) attempted to open the link which opened the box shown in the image below:

 

Capture.PNG

User3 clicked 'Next' which took them to a page where they were invited to enter an email address. They entered their own email address and received access denied (as expected). However, when they entered the email address of user2, they were granted access and were able to see the video.

 

At no point did User3 enter the password of User2.

User1 did not grant access to User3.

 

Can anyone suggest what might have happened here? I cannot get the box shown in the image above to appear and therefore I cannot fully replicate the issue at this time. I wonder if this is a bug with the option to enter an email address bypassing the requirement for a password?

2 Replies

@Kotus-Tech I feel like this is a test with a trick question :) Did user3 use the same workstation as user2? That's the only explanation I can think of... You can't authenticate if you don't provide credentials so the only thing I can think of is that the user did not authenticate at all because the authentication had already taken place... 

 

 

best response confirmed by Kotus-Tech (Iron Contributor)
Solution

@talpeerLOL I'm glad it isn't just me! Apparently the machine contained no other user details.

 

I am going to write this off as a user error, I cannot see any possibility that permissions were breached in this manner.

1 best response

Accepted Solutions
best response confirmed by Kotus-Tech (Iron Contributor)
Solution

@talpeerLOL I'm glad it isn't just me! Apparently the machine contained no other user details.

 

I am going to write this off as a user error, I cannot see any possibility that permissions were breached in this manner.

View solution in original post