I agree with Christian. I never saw that error recently until I removed "can read on Website" from the public role. For a while I added that to public role to prevent a redirect loop 502 which was occuring instead of the no access page for users with no roles or the public role. So that permission was added as temp work around until the redirect loop error was recently patched. And now I see this "Access is denied" immediately after logging in via oauth.
On Wed, Oct 27, 2021 at 1:15 AM Christian Schilling < [email protected]> wrote: > Hi Lewis, > > sorry for the late answer, but I didn't have time for investigating the > issue yesterday. I took a look now. > I found the code where the alert is generated. > https://github.com/apache/airflow/blob/main/airflow/www/ > <https://github.com/apache/airflow/blob/main/airflow/www/templates/airflow/_messages.html> > auth.py > > There the authorization is checked. I followed the code there. My thought > is that when you call the airflow root first without permissions, this > alert is generated. Then you are redirected in the OAuth Flow until you get > back to the view with permissions, but the alert isn't deleted. > > What do you think. > > Chris > > Christian Schilling <[email protected]> schrieb am Mo., > 25. Okt. 2021, 18:35: > >> Hi Lewis, >> >> ok cool, thanks. If we find where the rendering is triggered, it helps to >> find the root cause or at least to understand the process. Maybe I can have >> a look at it tomorrow :) >> >> Chris >> >> >> Lewis John McGibbney <[email protected]> schrieb am Mo., 25. Okt. 2021, >> 18:31: >> >>> Hi Christian, >>> >>> On 2021/10/25 16:23:47, Christian Schilling < >>> [email protected]> wrote: >>> > Does anyone know where the alert is >>> > generated? >>> >>> >>> https://github.com/apache/airflow/blob/main/airflow/www/templates/airflow/_messages.html >>> seems to be the dynamically rendered code block... I have no idea how to >>> even debug the code execution though. I am not a front end developer. >>> >>> lewismc >>> >>
