Re: OAUTH2 Problem with AzureAD

Hi Asmita, Kindly ignore the previous patch. Please use the v2 version. Thanks, Yogesh Mahajan EnterpriseDB On Thu, Apr 21, 2022 at 11:08 AM Yogesh Mahajan < yogesh.maha...@enterprisedb.com> wrote: > Hi Asmita, > > Here is a patch file which fixes RM7325 >

Re: OAUTH2 Problem with AzureAD

Hi Asmita, Here is a patch file which fixes RM7325 or you can use snapshot build from here to test once patch is committed. Thanks, Yogesh Mahajan EnterpriseDB On Wed, Apr 20, 2022 at 6:17

Re: OAUTH2 Problem with AzureAD

Hello Yogesh, Done. https://redmine.postgresql.org/issues/7325 Meanwhile, can the below change easily be incorporated in code to check if it works? if yes, then could you provide me the details. Also, the profile returned by Azure AD has the key 'mail' and current pgadmin code checks the value w

Re: OAUTH2 Problem with AzureAD

Hello Khushboo, I get below error if I use - *https://graph.microsoft.com/v1.0 / * This one is resp.json() o/p I printed. {'error': {'code': 'BadRequest', 'message': "Resource not found for the segment 'profile'.", 'innerError': {'date': '2022-04-20T09:37:23',

Re: OAUTH2 Problem with AzureAD

Hi, I was able to reproduce the issue. Below change is required in configuration - # Name of the Endpoint, ex: user 'OAUTH2_USERINFO_ENDPOINT': 'me', And Also, the profile returned by Azure AD has the key 'mail' and current pgadmin code checks the value with key = 'email' to retrieve user email

Re: OAUTH2 Problem with AzureAD

Hi, On Tue, Apr 19, 2022 at 11:30 PM Asmita Thapliyal < asmita.thapli...@gmail.com> wrote: > Hello! > > I have configured OAUTH2 with azure ad with below config > > 'OAUTH2_NAME': "azure", > > # The display name, ex: Google > > 'OAUTH2_DISPLAY_NAME': 'MS Azure', > >