Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Token type 'PFAT' is not supported for MSA scenario 'PFAT' #2620

Closed
A9G-Data-Droid opened this issue Aug 15, 2024 · 2 comments
Closed

Token type 'PFAT' is not supported for MSA scenario 'PFAT' #2620

A9G-Data-Droid opened this issue Aug 15, 2024 · 2 comments
Labels
Service issue type:bug A broken experience

Comments

@A9G-Data-Droid
Copy link

Describe the bug

I am seeing an intermittent error that started today:

Token type 'PFAT' is not supported for MSA scenario 'PFAT'

Out of 10 emails, two have failed with this error. So while I think it's server side there is also nothing on the internet about this error. Seems like I'm the first person to see or report it. So if there is any insight about what this error means, it would like to get it documented.

Expected behavior

My code has been sending many emails per day flawlessly for over a year.

How to reproduce

/// <summary>
/// Send email using the credentials and send from used in constructor.
/// </summary>
/// <param name="theEmail">A complete email message, use EmailTemplate to generate.</param>
/// <param name="cancelToken">To stop the request.</param>
[PublicAPI]
public async Task SendMailAsync(Message theEmail, CancellationToken cancelToken = new())
{
    // Define our new Microsoft Graph client. Use the credentials we specified above.
    using GraphServiceClient graphServiceClient = new GraphServiceClient(_existingCredentials, _scopes, _endpoint);

    var requestBody = new SendMailPostRequestBody
    {
        Message = theEmail,
        SaveToSentItems = true,
    };

    // Send mail as the given user. 
    var fromUser = graphServiceClient.Users[_sendAsUserID];
    await fromUser.SendMail.PostAsync(requestBody, null, cancelToken).ConfigureAwait(false);
}

SDK Version

5.56.0

Latest version known to work for scenario above?

5.56.0

Known Workarounds

If you send it again, it goes through. Likely a server issue?

Debug output

Click to expand log ```

{
"error": {
"code": "TokenTypeNotSupported",
"message": "Token type 'PFAT' is not supported for MSA scenario 'PFAT'",
"innerError": {
"oAuthEventOperationId": "-REDACTED-",
"oAuthEventcV": "PTLBqqwT525Pt4yTB0VD0Q.1",
"errorUrl": "https://aka.ms/autherrors#error-InvalidMsaTicket",
"requestId": "-REDACTED-",
"date": "2024-08-15T17:17:26"
}
}
}

</details>


### Configuration

- OS: Windows 10 x64

### Other information

I believe the issue is server side. Looking to confirm. 

Also, what's a PFAT?
@A9G-Data-Droid A9G-Data-Droid added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Aug 15, 2024
@andrueastman
Copy link
Member

Thanks for raising this @A9G-Data-Droid

Any chance you can post the same question at https://aka.ms/askGraph to get feedback from the API owners on whther this is expected? As this repo is mainly intended for sdk related issues, we may not be best placed to answer or give feedback on API related issues.

@andrueastman andrueastman added Service issue status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Aug 16, 2024
@A9G-Data-Droid
Copy link
Author

I got the following response:

Our engineering team has found a change they believe had caused this issue. They're reverted the change and are seeing improvement. If you could please help us confirm the issues are since resolved? For reference, you should see communications posted under EX862948 in your Service Health Dashboard.

This confirms it is not an SDK issue. If you receive this error, there is nothing wrong with your code. It is server side.

@microsoft-github-policy-service microsoft-github-policy-service bot removed the status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close label Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Service issue type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

2 participants