We have a site used by Outlook addin hosted on sharepoint, when a user tried to access it they had a browser window open on the Sharepoint Online site, our front end is hosted there but it doesn't bring us to site location it just brings to Sharepoint home page.
We resolved this for a lot of users by adding runtimes in our manifest (this will force Outlook to use IE, whereas before browser is determined on a combination of 365 and windows versions). Still for some users it will bring us to a new browser, we have checked they are on the same Windows and Office 365 version as others who have the plugin working in Outlook task pane.
Also to note there is no issue with anyone using the plugin from OWA (web mail in a browser) and the redirect from desktop outlook looks like it for SSO then verifies user in browser and brings us to Sharepoint.
anyone have any idea what could be causing this?
The problem was caused by any sites or domains trying to be accessed by outlook addin need to be added to app domains in the manifest file. We ran a fiddler trace on the users machine and took a list of the domains that were being hit (for SSO) once we added them this issue was resolved.
We have setup and are hosting a centrally deployed Add-in for Excel developed with the OfficeJS API. We have had success in building, hosting, and testing the Add-in, but are now seeing a very strange issue that we are having trouble debugging. For context, the Add-in is developed with React, the OfficeJS API, and is intended to be loaded within Excel and primarily interacted with via the taskpane window.
Now that we have a working Add-in, we have deployed the Add-in to our first client using Centralized Deployment (https://learn.microsoft.com/en-us/office/dev/add-ins/publish/centralized-deployment) for the Client's associated Office 365 account. When deploying, we originally only deployed to a certain subset of users while finalizing testing, but since we have updated the "Assign Users" setting to "Everyone". We are now running into a strange issue where some of our users in the account are able to access the add-in, and some are not. It should also be noted that all of the users who originally had access still have access; it seems only a subset of the newly authorized users are unable to access the add-in.
So far, we have tried a number of things to re-create and/or resolve the issue, but have had no success:
Setting up new accounts - when setting up a new account, the new account seems to have access to the Add-in as expected. We are unable to re-create the bad state some users are experiencing.
Clearing Excel Cache - we have had users clear their Excel application and web cache, but nether has resulted in changes to access.
Logging in/out - we have worked with users to sign-out, clear cache, and sign-in again but this does not update any access settings for the Add-in.
Attempting to Manually "Insert" the Add-in - when opening the "Insert" tab and selecting "My Add-ins" menu from Excel, the user does not have the Add-in listed under the "Admin Managed" tab. If the user attempts to "Refresh" it still does not change anything.
We are starting to meet with some of the users who are experiencing the issue to further investigate, so any advice or further debugging tips would be greatly appreciated!
We are writing a document organization system as a Custom Tab within Microsoft Teams and we are trying to replicate the 'Edit in Teams' option that´s provided by Microsoft Teams on the Files tab but it seems that we are unable to replicate the functionality. We are storing files within Sharepoint and have an edit URL, but we are unable to iframe this link due to CORS issues and can only open this link in a new browser. Does anyone have any thoughts on how we can open office documents within the teams client from a custom tab other than opening as a new window which means users have to keep switching in and out of Microsoft Teams.
By looking at what Microsoft teams is doing via the network requests, when you select ´Edit in Teams' it is getting hold of an wacUrlEdit link which appears to be iframeable which for example begins with https://euc-word-edit.officeapps.live.com/we/wordeditorframe.aspx?ui=en, however we can´t get hold of this wacUrlEdit link as it generated using an access token from https://api.spaces.skype.com, which according to https://stackoverflow.com/users/4406395/bill-bliss-msft on How to get an Azure Active Directory access token for https://api.spaces.skype.com isn´t publicly available, it´s only intended for the teams client. Fyi.. It also seems that Teams doesn´t IFrame this wacUrlEdit, but opens up a new url (at least in the web browser) via https://teams.microsoft.com/_#/docx/viewer/teams
I have read about WOPI host implementation, but this does seem like a lot of work to solve this and not totally sure this is the correct option considering these files are stored in Sharepoint Online.
I have created a test SharePoint server to be as close to our production server as possible. Production SharePoint databases were backed up and restored to our test server. The three main web.configs (Central Admin, main site, Security Token Service Application) were modified to include our custom app settings.
The site comes up fine, logging in using both AD and our custom FBA membership provider works as well.
Certain pages are visible in the Site Libraries through View All Site Content and using SharePoint Designer but SharePoint says that the page(s) are not found if you try to view them or check them in. Not all pages are not available. If I delete a bad page and replace it with a copy from our production application, it displays fine.
I've already found and tried possible solutions such as restarting the Search Query and Site Settings Service and checking the Alternate Access Mapping. I also found a possible solution that has you go to Component Services and modify security relative to an OSearch14 property. I was not able to modify this since right clicking on the property did not pop up any menu options. I will continue to look into this.
Any Ideas? I appreciate any help.
Thanks.
Our environment is Sharepoint 2010, with a web application created (and site collection on top), using claims based authentication. The first site is using port 881. It is using integrated windows authentication. Another web application is created, extending the first application, using port 882. This site is using Forms Based Authentication, the membership provider is System.Web.Security.ActiveDirectoryMembershipProvider, named admembers. I have turned off Client Integration on both sites.
When I login to the 881 site, on my corporate network, logged into the machine with the same domain account that sharepoint uses, I can open an Office file saved in a document library, and it subsequently opens in the appropriate Office application, without asking me login again. But, If I login to Sharepoint from a computer that is not on our network, or login to the computer with an account that is not a domain account, I get prompted again to login when openning an Office document. If I choose the option to save, it does not prompt, but if I choose open in the dialog window, I am forced to enter my domain credentials again.
When I login to the 882 site, which uses FBA, I experience the same problem. If I open an Office document, the appropriate Office application opens, and asks me for my credentials, by showing me a dialog window with the sign in page loaded. If I choose to save the file, then I am not prompted to login, and the file saves to a local folder.
I can't expect my users that are off site to login again everytime they open an Office document, like Work, Excel, Powerpoint, etc. I have tried numerous fixes, including disabling client integration, changing the browser handling mode (strict/permissive), changing internet explorer settings (for integrated windows authentication), changing the integrated windows authentication site to use basic authentication, even hacking the page using jquery to call the sharepoint javascript function that execute the "download a copy" function. None of them work: when choosing to "open" the Office document in the browser, the user has to login again, or just close the dialog window without logging in (as long as client integration for the zone is turned off).
I'm looking to get this accomplished using windows authentication or forms based authentication.
Help!
I found this answer in a similar post which seemed to fix the problem for me when I tested it. The gist of it is you need to deny the HTTP Verbs OPTIONS and PROPFIND in IIS. Having said this, I'm not an IIS guru and am not exactly sure what this means or what else it might affect. Can anyone else shed some light on this?
A bit of background, I'm using SharePoint 2010, on an FBA site.
You have the standard three use cases:
Employee intranet access
Employee remote access
Partner remote access
Employee intranet access
This normally always works out of the box, and it looks like it is working for you.
Employee remote access
The only way that i have seen this work (and i have tried many ways) is to get TMG or ISA. Basically ISA is setup in FORMS auth with SSL, it captures the auth details, and then passes them to the sharepoint server. (and other servers if you have them eg OWA for sharepoint mail web parts)
If you select the "Is private computer" option on the ISA login screen, then Office documents share the auth cookie and don't prompt for another login. I had so many problems, but as soon as i installed TMG, they all went away. I would not recommend any other approach now.
The added bonus of this method, is that remote employees are treated as the same account as the intranet user. The way you are setup with a seperate web application, means that they will be different accounts, so things like [checkout/modifiedby/createdby/personalisation] will be different accounts (though they look the same)
Partner remote access
This may never ever work on some clients (especially Vista), as IE needs to share the authentication with Office
If this is sharepoint 2010, try this.
Get-SPSecurityTokenServiceConfig
Look at your UseSessionCookies value in the output. If True, apply the powershell below.
$sts = Get-SPSecurityTokenServiceConfig
$sts.UseSessionCookies = $false
$sts.Update()
If UseSessionCookies is true, you will have to login to any docs u want to download...