Using Office.context.mailbox.getCallbackTokenAsync on a shared mailbox fails

[kworksltd]

Using Office.context.mailbox.item.getSharedPropertiesAsync on a shared mailbox fails. This also happens when using the Script Lab for Outlook add-in, using the shared mailbox example. The expected behaviour when selecting the 'Run operation as delegate on selected message' returns nothing. Debugging the code reveals the getSharedPropertiesAsync call is returning an error: OSF.DDA.Error, Code 9018, "GenericTokenError". I expect the add-in to show the email's properties but instead it shows nothing.

I have tried this on the web client for Outlook on Windows 10 and the latest Outlook Client on Windows 10. I have checked all the settings on the shared mailbox to ensure I have the correct permissions and that it is visible in GAL

[exextoc]

Can you share the code snippet you are using

[kworksltd]

This is the code taken from Script Lab for Outlook - the Perform operation as a delegate example.

$("#get").click(get);
$("#run-message").click(runOnMessage);
$("#run-appointment").click(runOnAppointment);

function get() {
  if (!Office.context.mailbox.item.getSharedPropertiesAsync) {
    console.error("Try this sample on an item from a shared folder.");
    return;
  }

  Office.context.mailbox.item.getSharedPropertiesAsync(function(result) {
    console.log(result.value);
  });
}

function runOnMessage() {
  if (!Office.context.mailbox.item.getSharedPropertiesAsync) {
    console.error("Try this sample on a message from a shared folder.");
    return;
  }

  Office.context.mailbox.getCallbackTokenAsync({ isRest: true }, function(result) {
    if (result.status === Office.AsyncResultStatus.Succeeded && result.value !== "") {
      Office.context.mailbox.item.getSharedPropertiesAsync(
        {
          // Pass auth token along.
          asyncContext: result.value
        },
        function(result2) {
          let sharedProperties = result2.value;
          let delegatePermissions = sharedProperties.delegatePermissions;

          // Determine if user has the appropriate permission to do the operation.
          if ((delegatePermissions & Office.MailboxEnums.DelegatePermissions.Read) != 0) {
            var ewsId = Office.context.mailbox.item.itemId;
            var restId = Office.context.mailbox.convertToRestId(ewsId, Office.MailboxEnums.RestVersion.v2_0);
            let rest_url =
              sharedProperties.targetRestUrl + "/v2.0/users/" + sharedProperties.targetMailbox + "/messages/" + restId;

            $.ajax({
              url: rest_url,
              dataType: "json",
              headers: { Authorization: "Bearer " + result2.asyncContext }
            })
              .done(function(response) {
                console.log(response);
              })
              .fail(function(error) {
                console.error(error);
              });
          }
        }
      );
    }
  });
}

function runOnAppointment() {
  if (!Office.context.mailbox.item.getSharedPropertiesAsync) {
    console.error("Try this sample on an appointment from a shared folder.");
    return;
  }

  Office.context.mailbox.getCallbackTokenAsync({ isRest: true }, function(result) {
    if (result.status === Office.AsyncResultStatus.Succeeded && result.value !== "") {
      Office.context.mailbox.item.getSharedPropertiesAsync(
        {
          // Pass auth token along.
          asyncContext: result.value
        },
        function(result2) {
          let sharedProperties = result2.value;
          let delegatePermissions = sharedProperties.delegatePermissions;

          // Determine if user has the appropriate permission to do the operation.
          if ((delegatePermissions & Office.MailboxEnums.DelegatePermissions.Read) != 0) {
            var ewsId = Office.context.mailbox.item.itemId;
            var restId = Office.context.mailbox.convertToRestId(ewsId, Office.MailboxEnums.RestVersion.v2_0);
            let rest_url =
              sharedProperties.targetRestUrl + "/v2.0/users/" + sharedProperties.targetMailbox + "/events/" + restId;

            $.ajax({
              url: rest_url,
              dataType: "json",
              headers: { Authorization: "Bearer " + result2.asyncContext }
            })
              .done(function(response) {
                console.log(response);
              })
              .fail(function(error) {
                console.error(error);
              });
          }
        }
      );
    }
  });
}

[exextoc]

Can you check if getCallbackTokenAsync api alone returns the token as expected for your account?

[kworksltd]

Yes - this works fine for emails in my account. Kind regards, Sharad Sharad Patel Filestar Tel: 0203 318 3113 ext 2 Mobile: 0780 1657 052 Web: filestar.eu

…

________________________________ From: Outlook Add-ins Team - MSFT ***@***.***> Sent: Thursday, October 12, 2023 2:01:37 PM To: OfficeDev/office-js ***@***.***> Cc: kworksltd ***@***.***>; Author ***@***.***> Subject: Re: [OfficeDev/office-js] Using Office.context.mailbox.item.getSharedPropertiesAsync on a shared mailbox fails (Issue #3748) Can you check if getCallbackTokenAsync api alone returns the token as expected for your account? — Reply to this email directly, view it on GitHub<#3748 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAURKBHSPJKCSBHANBTXXJLX67S3DANCNFSM6AAAAAA55M2DGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[exextoc]

@kworksltd The error mentioned above is related to token API and not specific to getSharedPropertiesAsync
Could you please confirm if getCallbackTokenAsync api is working in the shared account by running below code?
Sample code:
Office.context.mailbox.getCallbackTokenAsync(
function (asyncResult)
{
console.log(JSON.stringify(asyncResult));
}
);

[kworksltd]

It is the getCallbackTokenAsync call (on the shared folder - works fine on the non-shared folder) that is returning the error. Please see the attached screenshot for the code and response in a debug window for Edge. The console window at the bottom shows the error. Although this is my code, I get the same response from the Script Lab sample I originally posted.

[exextoc]

Thanks for confirming. Has this been working previously, and have you only started receiving the error recently?

[kworksltd]

This has been working perfectly for non-shared inboxes (and still does). Recently we added support for shared inboxes and therefore followed the Script Lab example on how to get the content for an email from a shared inbox and obtain a token for the shared inbox. This is when we encounter the issue. Our getEmailCallbackToken routine (as shown in my previous screenshot) returns a token just fine for a non-shared inbox, but returns the error when it is a shared inbox. Kind regards, Sharad Sharad Patel Filestar Support [cid:fe3886a5-0736-417f-be28-56dff8dacb08] <http://filestar.eu/>

…

________________________________ From: Outlook Add-ins Team - MSFT ***@***.***> Sent: Tuesday, October 17, 2023 15:19 To: OfficeDev/office-js ***@***.***> Cc: kworksltd ***@***.***>; Mention ***@***.***> Subject: Re: [OfficeDev/office-js] Using Office.context.mailbox.item.getSharedPropertiesAsync on a shared mailbox fails (Issue #3748) Thanks for confirming. Has this been working previously, and have you only started receiving the error recently? — Reply to this email directly, view it on GitHub<#3748 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAURKBFMFFZTYGUWAS5W6FDX72HVNAVCNFSM6AAAAAA55M2DG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRWGUYTONJZGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[sahanar28]

Hi, @exextoc Even I am facing the same issue with Using Office.context.mailbox.getCallbackTokenAsync on a shared mailbox with the exact same error message and error code. I have already raised a github ticket for it. Is this issue fixed or when can we expect it be fixed?

[kworksltd]

@kworksltd - Some fixes related to shared mailbox went in recently and changes are rolled out to prod. Can you please try again and check if you are still facing the issue?

I have tested this again today and I am still getting the same error response when using the shared inbox. is there a sample add-in you can provide to test this outside of our own code? Outlook Script-Lab that I had previously used to test this is now having its own problem (already reported).

[exextoc]

@kworksltd Could you please confirm which Extension point is being used by your Add-in here?

[kworksltd]

The Extension point in my add-in is MessageReadCommandSurface

[exextoc]

Thanks for reporting this issue regarding shared mailbox. It has been put on our backlog. We unfortunately have no timelines to share at this point
 
Internal tracking id: Office: 4023303

[sajalsoni6]

@exextoc i'm still facing this issue. when will it be fixed?

[ingin97]

@exextoc We are also facing this issue getting GenericTokenError (code 9018) when trying to obtain EWS or REST tokens for a shared mailbox, added as a shared folder.

[parlato-vooma]

@exextoc we're facing the same issue; getting a GenericTokenError (code 9018) when trying to fetch an access token. Code below; we're using https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js. This did appear to work for some time for us, and recently broke (within the last week, maybe). I don't think the users facing this issue are using a shared inbox, however - I'm not entirely sure what that means.

const getAccessToken = async () => {
  return new Promise<string>((resolve, reject) => {
    Office.context.mailbox.getCallbackTokenAsync(
      { isRest: true },
      function (result) {
        if (result.status === Office.AsyncResultStatus.Succeeded) {
          resolve(result.value);
        } else {
          reject(result.error);
        }
      }
    );
  });
};

[ajays-msft]

@kworksltd , @ingin97 -The shared mailbox token issue is now resolved. Fix is available in prod.

[kworksltd]

I can confirm that this is now working without presenting the error as originally submitted. I am therefore happy to mark this as closed.

[kdeshpande-methodcrm]

We are still facing the same issue. Do we know how this can be fixed? Or was there an update from Microsoft that we missed?

[mmanjaree-msft]

@kdeshpande-methodcrm Can you please open a separate issue and add repro steps and video/screenshot there

[kdeshpande-methodcrm]

@mmanjaree-msft My colleague has opened an issue here : #4583
As for the reproduction steps, the comment - #4583 (comment) has an example to demonstrate the same issue we are facing