Nikitha Chettiar
Nikitha Chettiar
Response from service team : Not yet, we are still looking into the root cause of expired subscriptions in the GET List response. Not related to the issue of expired...
@nikithauc Thank you for the update! I am closing this issue since this is solved. I will take it up to the docs to team to indicate the right one.
@nmetulev Thank you for this feature request! Adding to the description of this issue, we should discuss providing ways to modify the other client configs after the client is initialized.
@jimmywim This request will need some some more discussion with the Graph SDK team. I would like to know what is your take on this issue?
@jimmywim The Graph JS SDK works with the National Cloud instances, that is, `"graph.microsoft.com", "graph.microsoft.us", "dod-graph.microsoft.us", "graph.microsoft.de", "microsoftgraph.chinacloudapi.cn", "canary.graph.microsoft.com"` Please let me know if the case is otherwise.
@jacksonR5Star Thanks for reporting this issue! I will take a look at this shortly.
Thank you @ramya-rao-a for bringing up this point! I will have to learn more about this issue and I will get back to you.
@IgorLopLego You can try out the ChaosHandler.ts provided by the Graph JavaScript library and plug it in the middleware to mock the request. Example: https://github.com/microsoftgraph/msgraph-sdk-javascript/blob/9441382f7963fa782cd30a103af2632d7585e0a0/test/development/workload/PageIterator.ts#L116
To be considered with #500 and #499
@r4hulp can you try this workaround? 1. Set account as null during initialization. ``` const options:AuthCodeMSALBrowserAuthenticationProviderOptions: { account: null, // set it null first interactionType: InteractionType.PopUp , scopes: ["user.read", "mail.send"]...