I am developing an outlook web addin, in the taskpane I have a cookie sent from the server with httpOnly. For the same session cookie is handled correctly, when I close the task pane and re-open the cookie seems to be cleared.
This does not happen on Mac, does not happen on Windows when the browser used by outlook is IE11.
Seems to be happening only when the outlook uses edge as it's engine.
Is there something I can add in the manifest perhaps to avoid this cookie clearing?
Adding to #BrianClink's response, the session cookie probably works on most versions that use Internet Explorer to load the add-ins. Whenever an add-in is closed, Internet Explorer stays alive for a while, which probably preserves the session cookies. Since we switched to Microsoft Edge, this is no longer the case. So please don't rely on this behavior for preserving cookies.
Related
Since I couldn't find the answer after hours of searching, my first attempt was to load a WebView in React Native and point it to a custom CCP page hosted on my own server using Amazon Connect Streams. This is the method which seems well documented, but it is intended for desktops. It works great in Firefox on desktop and mobile (Android). When I try it in Chrome or the React Native WebView, it fails.
Developer tools on the desktop version of Chrome gives this error: Refused to display '<URL>' in a frame because it set 'X-Frame-Options' to 'sameorigin'. Obviously, I don't have control over Amazon's X-Frame-Options but I don't think that's really the main problem. The other error shown in the console is: amazon-connect.js:204 [2020-07-14T22:12:32.258Z] [WARN]: ACK_TIMEOUT occurred, attempting to pop the login page if not already open. WARN # amazon-connect.js:204 amazon-connect.js:205 [2020-07-14T22:12:32.262Z] [ERROR]: ACK_TIMEOUT occurred but we are unable to open the login popup. I don't know what to do about this one.
I've also looked at the AWS.Connect API documentation, but it only seems to allow the customer side of a connection.
Has this been done before? If so, could someone give the broad strokes of it? I want to create an app which can connect to the Amazon CCP and maintain the connection so the agent can get an alert as soon as a chat attempt comes in.
Alternative solutions would be appreciated as well.
Update: There is a library from Amazon called amazon-connect-chatjs which looks promising, but I'm not sure if it will allow for the agent side of the chat session. I'm reading about it now.
I have created a secure embedded report (using the new method released in 2019) as specified below:
https://powerbi.microsoft.com/en-us/blog/easily-embed-secure-power-bi-reports-in-your-internal-portals-or-websites/
I created this in an html page using the supplied iframe.
It works fine on windows firefox and edge. It does not work in windows chrome.
It works fine on mac chrome. It does not work on mac safari.
It fails on windows chrome after opening a new tab and asking for the login details, this tab then closes and the power BI symbol in the embedded report just flashes like it is loading but it never finishes.
On Mac safari the login fails. It looks like it gets caught in a loop of some kind.
I just want it working on windows chrome really.
I have tried clearing my complete browser cache, cookies, rebooting serveral times and allowing pop-ups with no luck.
It does not make a difference if I select "remember me" or not at the time of login.
I have the latest version of chrome.
Does anyone know how to resolve this or if this is a know issue?
Here is the embedded report. You won't be able to access it but it may give you an idea of the issue:
https://fir-trial-66e3f.firebaseapp.com/embedded-report.html
I also can't log into the PBI community with this account so that may be related. The account works fine logging in to PBI Service or desktop. It is a PBI trial Pro account.
I had the same issue, i solved it by disabling the "Prevent Cross-Site Tracking" in Safari Settings. This worked for me and my clients. I hope it works for you too
I had the same issue in chrome. Solved it by enabling "Allow all cookies" in chrome settings.
Trying to update my old-styled Safari extension with background HTML page according to native app extension. The extension should perform HTTP requests in a background mode, and the earlier version used the same cookies that Safari did. But after migrating to native code, NSURLSessionDataTask can't access cookies that Safari has anymore.
Can anyone suggest how can I manage this case? Unfortunately, I can't pass cookies via messages to 'native' code (they are httponly).
I am not sure whether it is an issue of FireBreath or an ActiveX specific thing or I have just forgotten something.
I want to a download a file in my plugin using a derivative of FB::DefaultBrowserStreamHandler, and FB::BrowserHost::createStream(). The file is only accessable if my http request is authenticated by a cookie.
The built FireBreath plugin is working under Chrome and FF, but not under IE. The thing is that under IE no session cookie is sent when analyzing the requests with Fiddler.
Thanks in advance.
This is a feature that isn't supported the way you need it to be in FireBreath's activex implementation of browserstreams. You'd have to go into the code and find a way to add support for setting the cookie manually, I'm afraid. The reason it works in npapi browsers is that the browser itself provides an API for making the request, which means it will provide proxy info and cookies. In IE we have to emulate that, and that emulation doesn't get the cookies.
I have created a web page based on the log-in (facebook) specs that works correctly through IE, Safari, Mozilla. I'm trying to set-up an ipad running a Kiosk software program. The link that I have works correctly, but when it comes to the sign-in on facebook it stalls via iPad/Kiosk software. I contacted the software support team with Kiosk, and this is what was said
"It looks like the problem is caused by Kiosk Pro's inability to open more than one window; this is a result of having to use Apple's UI Web View browser as the base browser of Kiosk Pro and is not something we can change. Opening your page in Safari or a desktop browser the Facebook page opens as a separate pop-up over top of your page, which remains open even after the Facebook page closes. In Kiosk Pro, since there is no way to open another window, the Facebook link is navigated to inside the main window and there is no way for the user to get back to your main page (short of hitting the home button or idle timing out) once they have finished the facebook process. Unfortunately, this is a structural issue that I don't have any easy solutions for."
Is there any work around, etc. that anyone can guide me to resolve this issue. What I'm trying to do, it use an ipad as a kiosk to allow people to "like" my store as they visit. However, I'm using the Kiosk software to prevent the user from accessing any further info, web browsing, etc.
Any help would be greatly appreciated, thanks