Upgrade module to use Microsoft Graph Apis instead of old windows apis

Created on 5 June 2025, 3 days ago

Problem/Motivation

We came across a client which is using this module for SSO and from the 1st of Feb 2025 the old windows.net apis are deprecated and will be completely downed by the end of June 2025. as per following documentation by Microsoft
https://techcommunity.microsoft.com/blog/microsoft-entra-blog/action-req...

As a result we have move to new apis from Microsoft to fulfill the requirement, we will have to port from old apis to new apis here is the document of difference of the APIs requests
https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-request-d...

Full document:
https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-audit-api...

Steps to reproduce

  1. Setup the openid connect module
  2. Setup the Azure application for the sso and add correct permissions to it
  3. Enable the openid connect windows aad module
  4. Select the plugin under openid connect module configuration
  5. Add client id, client secret, tenant id, authorize and token url
  6. Ckeck the "Use Graph API for user info" check box and save
  7. save
  8. try to login
  9. you will see and error while login and the login will not be successful
  10. Proposed resolution

    Upgrade the graph apis from windows to microsoft and update the api calls for those graph api through out the module

    API changes

    We will update the api calls from Windows Azure Ad graph apis to Microsoft Graph as per following document
    https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-request-d...

💬 Support request
Status

Active

Version

1.0

Component

Code

Created by

🇮🇳India kaustubhb Mumbai

Live updates comments and jobs are added and updated live.
  • API change

    Changes an existing API or subsystem. Not backportable to earlier major versions, unless absolutely required to fix a critical bug.

Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024