I got the same error when calling api from frontend. The workaround was to call the api (e.g. go to swagger) in the same window as the frontend - and accepting the warning. For me it had to be the same windows because when debugging frontend a separate browser instance is created