OAuth application setup error

Hi,

I have Workplace Search up and running on LTS 18 on AWS and it's working fine with a couple of data sources. I'm trying to configure a new oauth application (for a custom search UI application that we've built) and getting an error that reads "An unexpected error occurred". Any help would be highly appreciated.

Thanks!

Hi oariel,

I'm not totally sure that I'm following, so to clarify - you are configuring the OAuth Application for Workplace Search (/ws/org/settings/oauth)? The goal being to use the Search API to power a custom built UI?

If that's the case, can you share the Workplace Search server logs from when you get your "Unexpected Error?" It might also be helpful for you use CURL to demonstrate your current flow, so that we can see where in the flow you're having an issue.

We figured it out - thanks, Sean. The problem was related a reverse-proxy settings.

Question: Is there a way in EWS to add tags to documents which are indexed by the stock SharePoint/OneDrive connectors? We would like to add additional tags of our own so that our application will be able to filter them more effectively.

Hi Oren,

I'm glad to hear that you got it working.

There is not currently a way to index tags for either the Sharepoint or OneDrive source. However we will consider and evaluate that as a suggestion. In the mean time, organizing your documents into folders by tag might help.

Hi Sean,

This functionality is pretty important for us. We want to associate documents by context (for example, location), and each document can apply to more than one, so the folder approach will be very limited unless we duplicate documents. This capability is built-in in other products and it would be great if you can support it in the very near future.

Hi Oren

I'm not quite sure I know what you mean when you write "tags". I can't seem to find tags mentioned in the SharePoint API at a glance. Could you point me in the right direction?

Sorry, this is how we refer to them internally. I was referring to fields in a schema. So just like you can define your own fields in a custom connector schema, we'd like to be able to add additional fields to the out-of-the-box connectors such as SharePoint, OneDrive etc.