Sebastian

I can confirm the issue with the current version 6.3.0. Going back to 6.2.1 and AD authentication and membership service work fine.

This is a common security issue with javascript reading data asynchronosly from different hosts. In order to make it work you need to set the no-cors header in the fetch...

After using it for some days now in real working environment, this idea also came to my mind. A second needed category for my daily workflow would be "on hold"....