Re: [pgAdmin][PATCH] Add OAUTH2_SCOPE variable for scope configuration

From: Nico Rikken <nico(dot)rikken(at)alliander(dot)com>
To: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>, Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>
Cc: "pgadmin-hackers(at)lists(dot)postgresql(dot)org" <pgadmin-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [pgAdmin][PATCH] Add OAUTH2_SCOPE variable for scope configuration
Date: 2021-08-31 07:55:26
Message-ID: AM0PR08MB32521FBAF69A58B1BB2F7ACBF4CC9@AM0PR08MB3252.eurprd08.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Thanks for reviewing. Indeed this is a bandaid to expand the usability of the OAuth implementation. As I've written on the redmine issue as well https://redmine.postgresql.org/issues/6627 I've tested my usecase with a modified scope by patching the oauth2.py file in production. That works well for authentication from Microsoft Azure AD. Also Shy N reported this method to work. This patch just makes the scope configurable so it can be adopted to different use-cases.

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Nikhil Mohite 2021-08-31 08:29:29 Re: [pgAdmin][RM-4567]: Privileges revoked using SQL query on objects like tables does not correctly in SQL tab
Previous Message Akshay Joshi 2021-08-31 07:33:21 Re: Patch: Two-factor Authentication (RM #6543)