I think we solved it on our own. It’s not really an IFS question.

Hi @julfeng 

I’m interested to know how you solved it, as I am facing a similar issue when trying to access an IFS web service.

Thanks
Miraj

I have just solved it!

You have to insert a new rule into the HTTP Response header: Access-Control-Allow-Origin *. Please note that, instead of using the * that means everyone, you can specify a list of knowed url.

Sorry I got back so late, been busy. I agree with Luca’s response also you can create a server based API that calls the IFS Rest, instead of the client going directly to the IFS REST call, that’s what we ended up doing. It’s a security issue when a browser directly calls a REST API from IFS I believe. In short, If you create your own API on the same server that calls the IFS API it will also solve the problem.

I’m not following what I need to do.  Is the Response Header in an XML file somewhere or is it accessible from the IFS Middleware Console?  If so where?  

I’m in the same boat.  I need to know where to put this information to pass along to the server team.

I am also having the same issue, We couldnt get this ‘ Access-Control-Allow-Origin * ‘ worked? did this’ Access-Control-Allow-Origin *  work for anyone?

/Jeewan