From lutfi.dwedari at pds.nl  Sun Oct  2 01:31:43 2016
From: lutfi.dwedari at pds.nl (Lutfi Dwedari)
Date: Sat, 1 Oct 2016 23:31:43 +0000
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine
Message-ID: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>

Hi.

I’m really struggling to get windows integrated authentication through Kerberos to work with QtWebEngine.
I’ve build the minimal and the demobrowser examples. They are working fine for normal http and https pages but not for pages that require integrated authentication.
When loading this pages I see that the authenticationRequired signal is emited.
I’ve read that apparently Chromium requires to specify a white list of servers that are allowed Kerberos/negotiate authentication.
I’ve tried setting the HLKM\Software\Policies\Chromium\AuthServerWhitelist as suggested here<https://dev.chromium.org/administrators/policy-list-3#AuthServerWhitelist>. But it has not worked.
I’ve also seen that there is a possibility to send parameters to Chromium but I’m not sure how to send from my application through the QtWebEngineProcess to Chromium. I may also still not work.

So my question. Has anyone tried integrated authentication? Is there any test for this?
Is there a way to send parameters to Chromium?
Is there any way to enable logging for QtWebEngine/QtWebEngineProcess/Chromium to get an idea why the authentication is failing?

The version of QT I’m using is 5.6.1-1.

Thanks a lot.

Lutfi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161001/65192fe6/attachment.html>

From tangk at lemote.com  Mon Oct  3 16:26:51 2016
From: tangk at lemote.com (tangk at lemote.com)
Date: Mon, 3 Oct 2016 22:26:51 +0800
Subject: [Qtwebengine] about qtbrowserplugin?
Message-ID: <201610032145168420503@yahoo.com>

hi all,
    Now I want to develop a Firefox plugin, and the MDN say about three method to do it.
1.firebreath
2.juce
3.qtbrowserplugin

I want  to use qtbrowserplugin to do it, but I found that the source code is not updated from 6 or 7 years ago? do you know how can I found the url of the latest code ?

thanks very much.



chair.cole at yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161003/223abd3b/attachment.html>

From thuan at fmod.com  Tue Oct  4 02:09:45 2016
From: thuan at fmod.com (Thuan Seah Tan)
Date: Tue, 4 Oct 2016 11:09:45 +1100
Subject: [Qtwebengine] Seemingly random crashes in QtWebEngine. Qt 5.4.1 on
 Windows 7 to Windows 10
Message-ID: <CAPYdqw9Hc0v7yMEJpmpX1Ax0jb5BgzKPdwViZzkoXR63ubGzWg@mail.gmail.com>

Hi all,

I am a developer working on a software that is using QtWebEngine to display
a website of ours. Since releasing, we have received a number of seemingly
random crashes with not much luck reproducing it locally. I have posted a
few of the callstack in
https://forum.qt.io/topic/71159/tracking-down-qtwebengine-related-crashes-on-windows
and was advised to repost it here. Wondering if there is any way to track
down the crashes given the information provided in the callstacks?


Thanks,
Thuan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161004/de6c8609/attachment.html>

From me at the-compiler.org  Tue Oct  4 05:14:59 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 4 Oct 2016 05:14:59 +0200
Subject: [Qtwebengine] about qtbrowserplugin?
In-Reply-To: <201610032145168420503@yahoo.com>
References: <201610032145168420503@yahoo.com>
Message-ID: <20161004031459.vhlxmmjvyaujzd76@tonks>

Hi,

* tangk at lemote.com <tangk at lemote.com> [2016-10-03 22:26:51 +0800]:
> hi all,
>     Now I want to develop a Firefox plugin, and the MDN say about three method to do it.
> 1.firebreath
> 2.juce
> 3.qtbrowserplugin
> 
> I want  to use qtbrowserplugin to do it, but I found that the source code is not updated from 6 or 7 years ago? do you know how can I found the url of the latest code ?
> 
> thanks very much.

I'm guessing you're looking at this page?
https://developer.mozilla.org/en-US/Add-ons/Plugins/External_resources_for_plugin_creation

Like the parent page mentions, (NPAPI) plugins are obsolete, and so is
qtbrowserplugin probably:
https://developer.mozilla.org/en-US/Add-ons/Plugins

I'm pretty sure what you want to write is a Firefox *extension* (aka
add-on), which has nothing to do with the thing Firefox calls plugins,
or with Qt:
https://developer.mozilla.org/en-US/Add-ons

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161004/c53703e2/attachment.sig>

From alexandru.croitor at qt.io  Tue Oct  4 13:05:23 2016
From: alexandru.croitor at qt.io (Alexandru Croitor)
Date: Tue, 4 Oct 2016 11:05:23 +0000
Subject: [Qtwebengine] Seemingly random crashes in QtWebEngine. Qt 5.4.1
 on Windows 7 to Windows 10
In-Reply-To: <CAPYdqw9Hc0v7yMEJpmpX1Ax0jb5BgzKPdwViZzkoXR63ubGzWg@mail.gmail.com>
References: <CAPYdqw9Hc0v7yMEJpmpX1Ax0jb5BgzKPdwViZzkoXR63ubGzWg@mail.gmail.com>
Message-ID: <51E607EF-3C8E-4E18-99D8-E44DA8D61FA6@qt.io>

Hi,

I would suggest trying out a newer Qt WebEngine version than 5.4.1, specifically 5.6.1 or newer.
Multiple fixes were done since 5.4.1, which might be relevant to your crashes.

Regards, Alex.

On 04 Oct 2016, at 02:09, Thuan Seah Tan <thuan at fmod.com<mailto:thuan at fmod.com>> wrote:

Hi all,

I am a developer working on a software that is using QtWebEngine to display a website of ours. Since releasing, we have received a number of seemingly random crashes with not much luck reproducing it locally. I have posted a few of the callstack in https://forum.qt.io/topic/71159/tracking-down-qtwebengine-related-crashes-on-windows and was advised to repost it here. Wondering if there is any way to track down the crashes given the information provided in the callstacks?


Thanks,
Thuan
_______________________________________________
QtWebEngine mailing list
QtWebEngine at qt-project.org<mailto:QtWebEngine at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/qtwebengine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161004/a63130b4/attachment.html>

From lutfi.dwedari at pds.nl  Wed Oct  5 15:43:06 2016
From: lutfi.dwedari at pds.nl (Lutfi Dwedari)
Date: Wed, 5 Oct 2016 13:43:06 +0000
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine
In-Reply-To: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
References: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
Message-ID: <DB6PR0101MB2262A0A0DBF6B0F75B9976D795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>

Hi.

As I mentioned in my earlier email Chromium requires to white list the servers that use Kerberos authentication. That is done with the AuthServerWhitelist registry entry in Windows.
I’ve done a global search in the qt 5.6.1 source code for the word AuthServerWhitelist and could not find any.
Chromium 51.0.2704.63 source code does have those references:

android_webview\browser\aw_browser_context.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
android_webview\browser\aw_browser_context.cc:  pref_registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
android_webview\browser\aw_browser_context.h:extern const char kAuthServerWhitelist[];
android_webview\browser\aw_browser_policy_connector.cc:      policy::key::kAuthServerWhitelist, prefs::kAuthServerWhitelist,
android_webview\browser\net\aw_url_request_context_getter.cc:      prefs::kAuthServerWhitelist, user_pref_service,
chrome\browser\io_thread.cc:      prefs::kAuthServerWhitelist, local_state,
chrome\browser\io_thread.cc:  registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "xxx");
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "*");
chrome\browser\policy\configuration_policy_handler_list_factory.cc:  { key::kAuthServerWhitelist,
chrome\browser\policy\configuration_policy_handler_list_factory.cc:    prefs::kAuthServerWhitelist,
chrome\browser\prefs\command_line_pref_store.cc:      { switches::kAuthServerWhitelist, prefs::kAuthServerWhitelist },
chrome\common\chrome_switches.cc:const char kAuthServerWhitelist[]           = "auth-server-whitelist";
chrome\common\chrome_switches.h:extern const char kAuthServerWhitelist[];
chrome\common\pref_names.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
chrome\common\pref_names.h:extern const char kAuthServerWhitelist[];
chrome\test\data\policy\policy_test_cases.json:  "AuthServerWhitelist": {
chrome\test\data\policy\policy_test_cases.json:    "test_policy": { "AuthServerWhitelist": "localhost" },
components\policy\resources\policy_templates.json:          'name': 'AuthServerWhitelist',
net\http\http_auth_preferences_unittest.cc:TEST(HttpAuthPreferencesTest, AuthServerWhitelist) {
tools\android\kerberos\README.md:     *   AuthServerWhitelist: `*`

Also in the current codebase: https://cs.chromium.org/search/?q=AuthServerWhitelist&sq=package:chromium

So it seems that the qtwebengine\src\3rdparty\chromium is missing files or that the code has been modified. For example in qt the file qtwebengine\src\3rdparty\chromium\chrome\common\chrome-switches.cc is missing these lines:
// Whitelist for Negotiate Auth servers
const char kAuthServerWhitelist[]           = "auth-server-whitelist";

Can anybody comment on this?

Thanks.
Lutfi

From: QtWebEngine [mailto:qtwebengine-bounces+lutfi.dwedari=pds.nl at qt-project.org] On Behalf Of Lutfi Dwedari
Sent: 02 October 2016 01:32
To: qtwebengine at qt-project.org
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine

Hi.

I’m really struggling to get windows integrated authentication through Kerberos to work with QtWebEngine.
I’ve build the minimal and the demobrowser examples. They are working fine for normal http and https pages but not for pages that require integrated authentication.
When loading this pages I see that the authenticationRequired signal is emited.
I’ve read that apparently Chromium requires to specify a white list of servers that are allowed Kerberos/negotiate authentication.
I’ve tried setting the HLKM\Software\Policies\Chromium\AuthServerWhitelist as suggested here<https://dev.chromium.org/administrators/policy-list-3#AuthServerWhitelist>. But it has not worked.
I’ve also seen that there is a possibility to send parameters to Chromium but I’m not sure how to send from my application through the QtWebEngineProcess to Chromium. I may also still not work.

So my question. Has anyone tried integrated authentication? Is there any test for this?
Is there a way to send parameters to Chromium?
Is there any way to enable logging for QtWebEngine/QtWebEngineProcess/Chromium to get an idea why the authentication is failing?

The version of QT I’m using is 5.6.1-1.

Thanks a lot.

Lutfi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161005/9d89badc/attachment.html>

From alexandru.croitor at qt.io  Wed Oct  5 15:45:38 2016
From: alexandru.croitor at qt.io (Alexandru Croitor)
Date: Wed, 5 Oct 2016 13:45:38 +0000
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine
In-Reply-To: <DB6PR0101MB2262A0A0DBF6B0F75B9976D795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
References: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<DB6PR0101MB2262A0A0DBF6B0F75B9976D795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
Message-ID: <F9DFD566-F2C6-4E6D-AD79-9E42F558EE93@qt.io>

Hi,

Qt WebEngine 5.6.1 is based on Chromium 45.
5.7.0 is based on Chromium 49
5.8 will be based on Chromium 53.

You could try the latest beta build of WebEngine 5.8.

Regards, Alex.

On 05 Oct 2016, at 15:43, Lutfi Dwedari <lutfi.dwedari at pds.nl<mailto:lutfi.dwedari at pds.nl>> wrote:

Hi.

As I mentioned in my earlier email Chromium requires to white list the servers that use Kerberos authentication. That is done with the AuthServerWhitelist registry entry in Windows.
I’ve done a global search in the qt 5.6.1 source code for the word AuthServerWhitelist and could not find any.
Chromium 51.0.2704.63 source code does have those references:

android_webview\browser\aw_browser_context.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
android_webview\browser\aw_browser_context.cc:  pref_registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
android_webview\browser\aw_browser_context.h:extern const char kAuthServerWhitelist[];
android_webview\browser\aw_browser_policy_connector.cc:      policy::key::kAuthServerWhitelist, prefs::kAuthServerWhitelist,
android_webview\browser\net\aw_url_request_context_getter.cc:      prefs::kAuthServerWhitelist, user_pref_service,
chrome\browser\io_thread.cc:      prefs::kAuthServerWhitelist, local_state,
chrome\browser\io_thread.cc:  registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "xxx");
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "*");
chrome\browser\policy\configuration_policy_handler_list_factory.cc:  { key::kAuthServerWhitelist,
chrome\browser\policy\configuration_policy_handler_list_factory.cc:    prefs::kAuthServerWhitelist,
chrome\browser\prefs\command_line_pref_store.cc:      { switches::kAuthServerWhitelist, prefs::kAuthServerWhitelist },
chrome\common\chrome_switches.cc:const char kAuthServerWhitelist[]           = "auth-server-whitelist";
chrome\common\chrome_switches.h:extern const char kAuthServerWhitelist[];
chrome\common\pref_names.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
chrome\common\pref_names.h:extern const char kAuthServerWhitelist[];
chrome\test\data\policy\policy_test_cases.json:  "AuthServerWhitelist": {
chrome\test\data\policy\policy_test_cases.json:    "test_policy": { "AuthServerWhitelist": "localhost" },
components\policy\resources\policy_templates.json:          'name': 'AuthServerWhitelist',
net\http\http_auth_preferences_unittest.cc:TEST(HttpAuthPreferencesTest, AuthServerWhitelist) {
tools\android\kerberos\README.md:     *   AuthServerWhitelist: `*`

Also in the current codebase: https://cs.chromium.org/search/?q=AuthServerWhitelist&sq=package:chromium

So it seems that the qtwebengine\src\3rdparty\chromium is missing files or that the code has been modified. For example in qt the file qtwebengine\src\3rdparty\chromium\chrome\common\chrome-switches.cc<http://chrome-switches.cc/> is missing these lines:
// Whitelist for Negotiate Auth servers
const char kAuthServerWhitelist[]           = "auth-server-whitelist";

Can anybody comment on this?

Thanks.
Lutfi

From: QtWebEngine [mailto:qtwebengine-bounces+lutfi.dwedari=pds.nl at qt-project.org] On Behalf Of Lutfi Dwedari
Sent: 02 October 2016 01:32
To: qtwebengine at qt-project.org<mailto:qtwebengine at qt-project.org>
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine

Hi.

I’m really struggling to get windows integrated authentication through Kerberos to work with QtWebEngine.
I’ve build the minimal and the demobrowser examples. They are working fine for normal http and https pages but not for pages that require integrated authentication.
When loading this pages I see that the authenticationRequired signal is emited.
I’ve read that apparently Chromium requires to specify a white list of servers that are allowed Kerberos/negotiate authentication.
I’ve tried setting the HLKM\Software\Policies\Chromium\AuthServerWhitelist as suggested here<https://dev.chromium.org/administrators/policy-list-3#AuthServerWhitelist>. But it has not worked.
I’ve also seen that there is a possibility to send parameters to Chromium but I’m not sure how to send from my application through the QtWebEngineProcess to Chromium. I may also still not work.

So my question. Has anyone tried integrated authentication? Is there any test for this?
Is there a way to send parameters to Chromium?
Is there any way to enable logging for QtWebEngine/QtWebEngineProcess/Chromium to get an idea why the authentication is failing?

The version of QT I’m using is 5.6.1-1.

Thanks a lot.

Lutfi
_______________________________________________
QtWebEngine mailing list
QtWebEngine at qt-project.org<mailto:QtWebEngine at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/qtwebengine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161005/7f2aa173/attachment.html>

From lutfi.dwedari at pds.nl  Wed Oct  5 15:53:11 2016
From: lutfi.dwedari at pds.nl (Lutfi Dwedari)
Date: Wed, 5 Oct 2016 13:53:11 +0000
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine
In-Reply-To: <F9DFD566-F2C6-4E6D-AD79-9E42F558EE93@qt.io>
References: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<DB6PR0101MB2262A0A0DBF6B0F75B9976D795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<F9DFD566-F2C6-4E6D-AD79-9E42F558EE93@qt.io>
Message-ID: <DB6PR0101MB22620ACFE16C664C26A1670795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>

Thanks Alexandru.

I thought it was Chromium 51 for QT 5.6.1. I misunderstood then this:

- Chromium Snapshot:
   * Security fixes from Chromium up to version 51.0.2704.63
   * [QTBUG-52602] Fixed devtools so it works with newer Chrome releases.
   * [QTBUG-52085, QTBUG-53108] qrc urls can now load local files.

http://code.qt.io/cgit/qt/qtwebengine.git/tree/dist/changes-5.6.1?h=5.6.1

Regards.

Lutfi.

From: Alexandru Croitor [mailto:alexandru.croitor at qt.io]
Sent: 05 October 2016 15:46
To: Lutfi Dwedari
Cc: qtwebengine at qt-project.org
Subject: Re: [Qtwebengine] Kerberos authentication not working in QtWebEngine

Hi,

Qt WebEngine 5.6.1 is based on Chromium 45.
5.7.0 is based on Chromium 49
5.8 will be based on Chromium 53.

You could try the latest beta build of WebEngine 5.8.

Regards, Alex.

On 05 Oct 2016, at 15:43, Lutfi Dwedari <lutfi.dwedari at pds.nl<mailto:lutfi.dwedari at pds.nl>> wrote:

Hi.

As I mentioned in my earlier email Chromium requires to white list the servers that use Kerberos authentication. That is done with the AuthServerWhitelist registry entry in Windows.
I’ve done a global search in the qt 5.6.1 source code for the word AuthServerWhitelist and could not find any.
Chromium 51.0.2704.63 source code does have those references:

android_webview\browser\aw_browser_context.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
android_webview\browser\aw_browser_context.cc:  pref_registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
android_webview\browser\aw_browser_context.h:extern const char kAuthServerWhitelist[];
android_webview\browser\aw_browser_policy_connector.cc:      policy::key::kAuthServerWhitelist, prefs::kAuthServerWhitelist,
android_webview\browser\net\aw_url_request_context_getter.cc:      prefs::kAuthServerWhitelist, user_pref_service,
chrome\browser\io_thread.cc:      prefs::kAuthServerWhitelist, local_state,
chrome\browser\io_thread.cc:  registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "xxx");
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "*");
chrome\browser\policy\configuration_policy_handler_list_factory.cc:  { key::kAuthServerWhitelist,
chrome\browser\policy\configuration_policy_handler_list_factory.cc:    prefs::kAuthServerWhitelist,
chrome\browser\prefs\command_line_pref_store.cc:      { switches::kAuthServerWhitelist, prefs::kAuthServerWhitelist },
chrome\common\chrome_switches.cc:const char kAuthServerWhitelist[]           = "auth-server-whitelist";
chrome\common\chrome_switches.h:extern const char kAuthServerWhitelist[];
chrome\common\pref_names.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
chrome\common\pref_names.h:extern const char kAuthServerWhitelist[];
chrome\test\data\policy\policy_test_cases.json:  "AuthServerWhitelist": {
chrome\test\data\policy\policy_test_cases.json:    "test_policy": { "AuthServerWhitelist": "localhost" },
components\policy\resources\policy_templates.json:          'name': 'AuthServerWhitelist',
net\http\http_auth_preferences_unittest.cc:TEST(HttpAuthPreferencesTest, AuthServerWhitelist) {
tools\android\kerberos\README.md:     *   AuthServerWhitelist: `*`

Also in the current codebase: https://cs.chromium.org/search/?q=AuthServerWhitelist&sq=package:chromium

So it seems that the qtwebengine\src\3rdparty\chromium is missing files or that the code has been modified. For example in qt the file qtwebengine\src\3rdparty\chromium\chrome\common\chrome-switches.cc<http://chrome-switches.cc/> is missing these lines:
// Whitelist for Negotiate Auth servers
const char kAuthServerWhitelist[]           = "auth-server-whitelist";

Can anybody comment on this?

Thanks.
Lutfi

From: QtWebEngine [mailto:qtwebengine-bounces+lutfi.dwedari=pds.nl at qt-project.org] On Behalf Of Lutfi Dwedari
Sent: 02 October 2016 01:32
To: qtwebengine at qt-project.org<mailto:qtwebengine at qt-project.org>
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine

Hi.

I’m really struggling to get windows integrated authentication through Kerberos to work with QtWebEngine.
I’ve build the minimal and the demobrowser examples. They are working fine for normal http and https pages but not for pages that require integrated authentication.
When loading this pages I see that the authenticationRequired signal is emited.
I’ve read that apparently Chromium requires to specify a white list of servers that are allowed Kerberos/negotiate authentication.
I’ve tried setting the HLKM\Software\Policies\Chromium\AuthServerWhitelist as suggested here<https://dev.chromium.org/administrators/policy-list-3#AuthServerWhitelist>. But it has not worked.
I’ve also seen that there is a possibility to send parameters to Chromium but I’m not sure how to send from my application through the QtWebEngineProcess to Chromium. I may also still not work.

So my question. Has anyone tried integrated authentication? Is there any test for this?
Is there a way to send parameters to Chromium?
Is there any way to enable logging for QtWebEngine/QtWebEngineProcess/Chromium to get an idea why the authentication is failing?

The version of QT I’m using is 5.6.1-1.

Thanks a lot.

Lutfi
_______________________________________________
QtWebEngine mailing list
QtWebEngine at qt-project.org<mailto:QtWebEngine at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/qtwebengine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161005/2f9eb95c/attachment.html>

From lutfi.dwedari at pds.nl  Wed Oct  5 17:27:54 2016
From: lutfi.dwedari at pds.nl (Lutfi Dwedari)
Date: Wed, 5 Oct 2016 15:27:54 +0000
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine
In-Reply-To: <F9DFD566-F2C6-4E6D-AD79-9E42F558EE93@qt.io>
References: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<DB6PR0101MB2262A0A0DBF6B0F75B9976D795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<F9DFD566-F2C6-4E6D-AD79-9E42F558EE93@qt.io>
Message-ID: <DB6PR0101MB2262F0E76B1D5B2E04491A6995C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>

Hi Alex.

I’ve downloaded the source code of QT 5.8. When I look for AuthServerWhitelist, I only find:
chrome\common\chrome_switches.cc:const char kAuthServerWhitelist[]           = "auth-server-whitelist";
chrome\common\chrome_switches.h:extern const char kAuthServerWhitelist[];
net\http\http_auth_preferences_unittest.cc:TEST(HttpAuthPreferencesTest, AuthServerWhitelist) {

So basically an initialization of kAuthServerWhitelist which is not used anywhere except an unit test.
It seems that still quite some of the code to accept the Kerberos whitelist is missing.

I need to take a further look into the code itself.

Regards.
Lutfi

From: Alexandru Croitor [mailto:alexandru.croitor at qt.io]
Sent: 05 October 2016 15:46
To: Lutfi Dwedari
Cc: qtwebengine at qt-project.org
Subject: Re: [Qtwebengine] Kerberos authentication not working in QtWebEngine

Hi,

Qt WebEngine 5.6.1 is based on Chromium 45.
5.7.0 is based on Chromium 49
5.8 will be based on Chromium 53.

You could try the latest beta build of WebEngine 5.8.

Regards, Alex.

On 05 Oct 2016, at 15:43, Lutfi Dwedari <lutfi.dwedari at pds.nl<mailto:lutfi.dwedari at pds.nl>> wrote:

Hi.

As I mentioned in my earlier email Chromium requires to white list the servers that use Kerberos authentication. That is done with the AuthServerWhitelist registry entry in Windows.
I’ve done a global search in the qt 5.6.1 source code for the word AuthServerWhitelist and could not find any.
Chromium 51.0.2704.63 source code does have those references:

android_webview\browser\aw_browser_context.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
android_webview\browser\aw_browser_context.cc:  pref_registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
android_webview\browser\aw_browser_context.h:extern const char kAuthServerWhitelist[];
android_webview\browser\aw_browser_policy_connector.cc:      policy::key::kAuthServerWhitelist, prefs::kAuthServerWhitelist,
android_webview\browser\net\aw_url_request_context_getter.cc:      prefs::kAuthServerWhitelist, user_pref_service,
chrome\browser\io_thread.cc:      prefs::kAuthServerWhitelist, local_state,
chrome\browser\io_thread.cc:  registry->RegisterStringPref(prefs::kAuthServerWhitelist, std::string());
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "xxx");
chrome\browser\io_thread_unittest.cc:  pref_service()->SetString(prefs::kAuthServerWhitelist, "*");
chrome\browser\policy\configuration_policy_handler_list_factory.cc:  { key::kAuthServerWhitelist,
chrome\browser\policy\configuration_policy_handler_list_factory.cc:    prefs::kAuthServerWhitelist,
chrome\browser\prefs\command_line_pref_store.cc:      { switches::kAuthServerWhitelist, prefs::kAuthServerWhitelist },
chrome\common\chrome_switches.cc:const char kAuthServerWhitelist[]           = "auth-server-whitelist";
chrome\common\chrome_switches.h:extern const char kAuthServerWhitelist[];
chrome\common\pref_names.cc:const char kAuthServerWhitelist[] = "auth.server_whitelist";
chrome\common\pref_names.h:extern const char kAuthServerWhitelist[];
chrome\test\data\policy\policy_test_cases.json:  "AuthServerWhitelist": {
chrome\test\data\policy\policy_test_cases.json:    "test_policy": { "AuthServerWhitelist": "localhost" },
components\policy\resources\policy_templates.json:          'name': 'AuthServerWhitelist',
net\http\http_auth_preferences_unittest.cc:TEST(HttpAuthPreferencesTest, AuthServerWhitelist) {
tools\android\kerberos\README.md:     *   AuthServerWhitelist: `*`

Also in the current codebase: https://cs.chromium.org/search/?q=AuthServerWhitelist&sq=package:chromium

So it seems that the qtwebengine\src\3rdparty\chromium is missing files or that the code has been modified. For example in qt the file qtwebengine\src\3rdparty\chromium\chrome\common\chrome-switches.cc<http://chrome-switches.cc/> is missing these lines:
// Whitelist for Negotiate Auth servers
const char kAuthServerWhitelist[]           = "auth-server-whitelist";

Can anybody comment on this?

Thanks.
Lutfi

From: QtWebEngine [mailto:qtwebengine-bounces+lutfi.dwedari=pds.nl at qt-project.org] On Behalf Of Lutfi Dwedari
Sent: 02 October 2016 01:32
To: qtwebengine at qt-project.org<mailto:qtwebengine at qt-project.org>
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine

Hi.

I’m really struggling to get windows integrated authentication through Kerberos to work with QtWebEngine.
I’ve build the minimal and the demobrowser examples. They are working fine for normal http and https pages but not for pages that require integrated authentication.
When loading this pages I see that the authenticationRequired signal is emited.
I’ve read that apparently Chromium requires to specify a white list of servers that are allowed Kerberos/negotiate authentication.
I’ve tried setting the HLKM\Software\Policies\Chromium\AuthServerWhitelist as suggested here<https://dev.chromium.org/administrators/policy-list-3#AuthServerWhitelist>. But it has not worked.
I’ve also seen that there is a possibility to send parameters to Chromium but I’m not sure how to send from my application through the QtWebEngineProcess to Chromium. I may also still not work.

So my question. Has anyone tried integrated authentication? Is there any test for this?
Is there a way to send parameters to Chromium?
Is there any way to enable logging for QtWebEngine/QtWebEngineProcess/Chromium to get an idea why the authentication is failing?

The version of QT I’m using is 5.6.1-1.

Thanks a lot.

Lutfi
_______________________________________________
QtWebEngine mailing list
QtWebEngine at qt-project.org<mailto:QtWebEngine at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/qtwebengine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161005/ae29b471/attachment.html>

From alexandru.croitor at qt.io  Wed Oct  5 17:47:40 2016
From: alexandru.croitor at qt.io (Alexandru Croitor)
Date: Wed, 5 Oct 2016 15:47:40 +0000
Subject: [Qtwebengine] Kerberos authentication not working in QtWebEngine
In-Reply-To: <F065F3A6-F94C-4F2A-AC6B-59036C81735F@qt.io>
References: <DB6PR0101MB22625CB1571826FBDFF1BEBF95C00@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<DB6PR0101MB2262A0A0DBF6B0F75B9976D795C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<F9DFD566-F2C6-4E6D-AD79-9E42F558EE93@qt.io>
	<DB6PR0101MB2262F0E76B1D5B2E04491A6995C40@DB6PR0101MB2262.eurprd01.prod.exchangelabs.com>
	<F065F3A6-F94C-4F2A-AC6B-59036C81735F@qt.io>
Message-ID: <7E6A4FEB-1795-48D5-AD07-0808E2D3EACE@qt.io>

Hi,


Resending message, because it got caught in moderator approval nonsense for some reason.

----------------

Some components of Chromium are removed from WebEngine to reduce memory usage and compilation times.

It might be the case for Kerberos. But I didn't try to search for it.

You can find the exclusion rules in qtwebengine/src/tools/scripts/take_snapshot.py and compare the relevant paths with the implementation files you find in Chrome itself.

Regards, Alex.

From e-ruei1 at ti.com  Thu Oct  6 16:32:26 2016
From: e-ruei1 at ti.com (Ruei, Eric)
Date: Thu, 6 Oct 2016 14:32:26 +0000
Subject: [Qtwebengine] QT5.6 Webengine demo browser carshes at
 ClientUsageTracker::AddCachedOrigin
Message-ID: <009C030982313E4589C6BC55FBF1E82A142D4251@DFLE09.ent.ti.com>

To whom it may concern:

This was originally posted at QT E2E Forum and someone suggested that this is a better place to get specific help.


 have dealt with a strange problem for quite some time and I need some advice to proceed.

Here are our system configurations:
TI AM57xx EVM
OS: Linux: 4.4.19
QT 5.6
QT WebEngine with chromium browser 45

The qtwebengine(widget) demo browser works for all general operations except it crashes at html5test.com<http://html5test.com/> while running HTML5Test.

With QTCreator remote debugger, I found that the program was crashed at

void ClientUsageTracker::AddCachedOrigin(
const GURL& origin, int64 new_usage) {
DCHECK(IsUsageCacheEnabledForOrigin(origin));

std::string host = net::GetHostOrSpecFromURL(origin);
int64* usage = &cached_usage_by_host_[host][origin]; // last instruction
int64 delta = new_usage - *usage;
*usage = new_usage;
if (delta) {
if (IsStorageUnlimited(origin))
global_unlimited_usage_ += delta;
else
global_limited_usage_ += delta;
}
DCHECK_GE(*usage, 0);
DCHECK_GE(global_limited_usage_, 0);
}
Which can be traced to the segment fault occurs at
linaro-2016.02/arm-linux-gnueabihf/include/c++/5.3.1/bits/basic_string.h (109)
template<typename _CharT, typename _Traits, typename _Alloc>
class basic_string
{
...
// Use empty-base optimization: http://www.cantrip.org/emptyopt.html
struct _Alloc_hider : allocator_type // TODO check __is_final
{
_Alloc_hider(pointer __dat, const _Alloc& __a = _Alloc())
: allocator_type(__a), _M_p(__dat) { }
...
}

The QT5 Webengine demo program crashes due to a std::map related memory allocation problem at the C++ class ClientUsageTracker where this class is only used by the html5 test code at html5test.com<http://html5test.com/>.

I am able to add the std::map test code at various places such as the demo program, qtwebengine module, other chromium module such as the "cert verify openssl" module and they all work fine. However, the demp program crashes when I add the similar test code at the module ClientUsageTracker.

typedef std::map<std::string, int64_t> UsageMap2;

ClientUsageTracker::ClientUsageTracker(
UsageTracker* tracker, QuotaClient* client, StorageType type,
SpecialStoragePolicy* special_storage_policy,
StorageMonitor* storage_monitor)
: tracker_(tracker),
client_(client),
type_(type),
storage_monitor_(storage_monitor),
global_limited_usage_(0),
global_unlimited_usage_(0),
global_usage_retrieved_(false),
special_storage_policy_(special_storage_policy) {

cout << "ClientUsageTracker::ClientUsageTracker" << endl;

#if 0
UsageMap2 temp;
int64_t *t = &temp["Hello"];

*t = 110;

cout << "lientUsageTracker::ClientUsageTracker = " << *t <<endl;

#endif

DCHECK(tracker_);
DCHECK(client_);
if (special_storage_policy_.get())
special_storage_policy_->AddObserver(this);
}

If you have any idea or advice, please let me know. If you don't, please ignore this one. It is highly appreciated that you have read this e-mail.

Best regards,

Eric
reply<https://forum.qt.io/topic/72002/qt5-6-webengine-demo-browser-carshes-at-clientusagetracker-addcachedorigin> quote<https://forum.qt.io/topic/72002/qt5-6-webengine-demo-browser-carshes-at-clientusagetracker-addcachedorigin>  <https://forum.qt.io/topic/72002/qt5-6-webengine-demo-browser-carshes-at-clientusagetracker-addcachedorigin> 0  <https://forum.qt.io/topic/72002/qt5-6-webengine-demo-browser-carshes-at-clientusagetracker-addcachedorigin>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161006/3a04e6d9/attachment.html>

From e-ruei1 at ti.com  Thu Oct  6 16:33:44 2016
From: e-ruei1 at ti.com (Ruei, Eric)
Date: Thu, 6 Oct 2016 14:33:44 +0000
Subject: [Qtwebengine] qtWebengine: Gstreamer support (roadmap)
Message-ID: <009C030982313E4589C6BC55FBF1E82A142D4267@DFLE09.ent.ti.com>

To whom it may concern:

It looks like the chromium browser uses ffpmsg as the default medium player backend and Samsung is working on a Gstreamer backend. Does anyone know about the medium player roadmap of qtWebengine. Will the qtWebengine support Gstreamer soon?

Best regards,

Eric

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161006/7f51875b/attachment.html>

From ville.voipio at iki.fi  Fri Oct  7 22:48:45 2016
From: ville.voipio at iki.fi (Ville Voipio)
Date: Fri, 7 Oct 2016 23:48:45 +0300
Subject: [Qtwebengine] Chromium/ffmpeg compile failure with RPi2
Message-ID: <4DF3AF16-2D67-4C04-87D6-805937E14982@iki.fi>

Hello, all!

I have been trying to compile QTWebengine for Raspberry Pi 2. Some weeks ago I succeeded in compiling it for RPi3, but now I am stuck with some obscure compilation problems.

QTWebEngine make stalls when compiling the following source file:

  qtwebengine/src/3rdparty/chromium/third_party/ffmpeg/libavcodec/vp8.c

The error message is an interesting one:

{standard input}: Assembler messages:
{standard input}:42: Error: bad instruction `ldrhcs r0,[r2],#2'
{standard input}:96: Error: bad instruction `ldrhcs r6,[ip],#2’

This looks as if the C compiler itself had emitted bad instruction codes which on the other hand does not seem very probable.  The instructions themselves do not look very suspicious (load register higher if carry set), but I am not very fluent in ARMv7 assembly.

The toolchain I am using is the Linaro toolchain invoked by:

  raspi2/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin/arm-linux-gnueabihf-gcc

where raspi2 is my build directory. The compiler version string is:

  arm-linux-gnueabihf-gcc (crosstool-NG linaro-1.13.1-4.8-2014.01 - Linaro GCC 2013.11) 4.8.3 20140106 (prerelease)

This is an old compiler, but it seems to be the recommended one for compiling QT5 for RPi, fresh out of github.com/raspberrypi/tools.

Googling this problem gives some hints that I am not the only one to have this problem, but I have not seen any resolution. Any ideas? Should I just force the QTWebEngine use system ffmpeg and then somehow obtain one (Raspbian seems to have libav instead)?

TIA,

- Ville

From viktor.engelmann at qt.io  Mon Oct 10 14:21:32 2016
From: viktor.engelmann at qt.io (Viktor Engelmann)
Date: Mon, 10 Oct 2016 14:21:32 +0200
Subject: [Qtwebengine] QT5.6 Webengine demo browser carshes at
 ClientUsageTracker::AddCachedOrigin
In-Reply-To: <009C030982313E4589C6BC55FBF1E82A142D4251@DFLE09.ent.ti.com>
References: <009C030982313E4589C6BC55FBF1E82A142D4251@DFLE09.ent.ti.com>
Message-ID: <2b72722c-c56b-7e83-690b-76c639ea5948@qt.io>

Hello Eric,

thanks for the useful information. I have filed a bug report:
https://bugreports.qt.io/browse/QTBUG-56443

kind regards

Viktor


Am 06.10.2016 um 16:32 schrieb Ruei, Eric:
>
> To whom it may concern:
>
>  
>
> This was originally posted at QT E2E Forum and someone suggested that
> this is a better place to get specific help.
>
>  
>
>  have dealt with a strange problem for quite some time and I need some
> advice to proceed.
>
> Here are our system configurations:
> TI AM57xx EVM
> OS: Linux: 4.4.19
> QT 5.6
> QT WebEngine with chromium browser 45
>
> The qtwebengine(widget) demo browser works for all general operations
> except it crashes at html5test.com <http://html5test.com/> while
> running HTML5Test.
>
> With QTCreator remote debugger, I found that the program was crashed at
>
> void ClientUsageTracker::AddCachedOrigin(
> const GURL& origin, int64 new_usage) {
> DCHECK(IsUsageCacheEnabledForOrigin(origin));
>
> ...
>
> The QT5 Webengine demo program crashes due to a std::map related
> memory allocation problem at the C++ class ClientUsageTracker where
> this class is only used by the html5 test code at html5test.com
> <http://html5test.com/>.
>
> I am able to add the std::map test code at various places such as the
> demo program, qtwebengine module, other chromium module such as the
> “cert verify openssl” module and they all work fine. However, the demp
> program crashes when I add the similar test code at the module
> ClientUsageTracker.
>
> ...
>
> If you have any idea or advice, please let me know. If you don’t,
> please ignore this one. It is highly appreciated that you have read
> this e-mail.
>
> Best regards,
>
> Eric
>
-- 

Viktor Engelmann
Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin

Viktor.Engelmann at qt.io
+49 151 26784521

http://qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161010/ea321058/attachment.html>

From mail at jiyuusoft.net  Thu Oct 20 22:10:19 2016
From: mail at jiyuusoft.net (mail)
Date: Thu, 20 Oct 2016 22:10:19 +0200
Subject: [Qtwebengine] WebEngine to Android Device
Message-ID: <9tqhb5t8ci76ds9y870qsj53.1476993707109@email.android.com>

Hi,
I've posted this message on interest at qt-project.org and I'd like to have the opinion of WebEngine developer :

I'm working on a project using a Web interface. This project should be cross-platform. Currently, I use WebEngineView on Windows, Linux and Mac and I use WebView on Android.
Unfortunately, and unless I am mistaken, WebView in Android is very limited (does not save login / password, do not save the configuration, not use ressource files,  ...)
Do you think it will be possible one day perhaps, to have WebViewEngine on Android or not have these limitations with WebView?
Bye



Best regards,



Charlie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161020/601b1b40/attachment.html>

From Kai.Koehne at qt.io  Fri Oct 21 13:29:04 2016
From: Kai.Koehne at qt.io (Kai Koehne)
Date: Fri, 21 Oct 2016 11:29:04 +0000
Subject: [Qtwebengine] WebEngine to Android Device
In-Reply-To: <9tqhb5t8ci76ds9y870qsj53.1476993707109@email.android.com>
References: <9tqhb5t8ci76ds9y870qsj53.1476993707109@email.android.com>
Message-ID: <DB6PR0201MB21352EEDD91B809273E24C5598D40@DB6PR0201MB2135.eurprd02.prod.outlook.com>



> -----Original Message-----
> From: QtWebEngine [mailto:qtwebengine-bounces+kai.koehne=qt.io at qt-
> project.org] On Behalf Of mail
> Sent: Thursday, October 20, 2016 10:10 PM
> To: qtwebengine at qt-project.org
> Subject: [Qtwebengine] WebEngine to Android Device
> 
>[...]
> Unfortunately, and unless I am mistaken, WebView in Android is very limited
> (does not save login / password, do not save the configuration, not use
> ressource files,  ...)
> 
> Do you think it will be possible one day perhaps, to have WebViewEngine on
> Android or not have these limitations with WebView?

I'm not too familiar with the internals of Qt WebView, but since it's just wrapping
the native API (i.e. android.webkit.* on Android) I think saving cookies etc should
be possible, but accessing resource files (qrc:///) is harder. If you're adventurous
you could have a peek yourself.

For Qt WebEngine, Chromium in theory does support Android, but there are no
immediate plans to support this for Qt WebEngine.

Regards

Kai

From mail at jiyuusoft.net  Fri Oct 21 15:15:59 2016
From: mail at jiyuusoft.net (=?utf-8?Q?Charles-=C3=89lie_Gentil?=)
Date: Fri, 21 Oct 2016 15:15:59 +0200
Subject: [Qtwebengine] WebEngine to Android Device
In-Reply-To: <DB6PR0201MB21352EEDD91B809273E24C5598D40@DB6PR0201MB2135.eurprd02.prod.outlook.com>
References: <9tqhb5t8ci76ds9y870qsj53.1476993707109@email.android.com>
	<DB6PR0201MB21352EEDD91B809273E24C5598D40@DB6PR0201MB2135.eurprd02.prod.outlook.com>
Message-ID: <0854B29D-1A7D-4FF1-9355-4340265210AF@jiyuusoft.net>

I know it is difficult (perhaps impossible) to access resources files.
In my case, the navigation information is not back ... anyway I do not know how



Charlie

mail at jiyuusoft.net
http://blog.jiyuusoft.net

> Le 21 oct. 2016 à 13:29, Kai Koehne <Kai.Koehne at qt.io> a écrit :
> 
> 
> 
>> -----Original Message-----
>> From: QtWebEngine [mailto:qtwebengine-bounces+kai.koehne=qt.io at qt-
>> project.org] On Behalf Of mail
>> Sent: Thursday, October 20, 2016 10:10 PM
>> To: qtwebengine at qt-project.org
>> Subject: [Qtwebengine] WebEngine to Android Device
>> 
>> [...]
>> Unfortunately, and unless I am mistaken, WebView in Android is very limited
>> (does not save login / password, do not save the configuration, not use
>> ressource files,  ...)
>> 
>> Do you think it will be possible one day perhaps, to have WebViewEngine on
>> Android or not have these limitations with WebView?
> 
> I'm not too familiar with the internals of Qt WebView, but since it's just wrapping
> the native API (i.e. android.webkit.* on Android) I think saving cookies etc should
> be possible, but accessing resource files (qrc:///) is harder. If you're adventurous
> you could have a peek yourself.
> 
> For Qt WebEngine, Chromium in theory does support Android, but there are no
> immediate plans to support this for Qt WebEngine.
> 
> Regards
> 
> Kai

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20161021/af6e4eaa/attachment.html>