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

HTTP Error 500: Currently unable to handle this request. #10158

Closed
CKeene78 opened this issue Jun 13, 2018 · 7 comments
Closed

HTTP Error 500: Currently unable to handle this request. #10158

CKeene78 opened this issue Jun 13, 2018 · 7 comments

Comments

@CKeene78
Copy link

Getting the title's error message when attempting to simply use the GraphFaceTemplate from the Azure Portal. Does prompt for authentication, I grant it, but I get the error whenever I try to navigate back to the Function URI. The function does not appear to even kick off as there is nothing either in the Logs nor in AppInsights.

Things I've checked:

  • Ensured Manifest file has "oauth2AllowImplicitFlow : true."
  • Function App has permissions to WAAD "Sign in and read user profile" and "View users' basic profile"

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@mimckitt
Copy link
Contributor

Thanks for the feedback! We are currently investigating and will update you shortly.

@mimckitt
Copy link
Contributor

@CKeene78 can you provide some screenshots of what you are seeing?

@CKeene78
Copy link
Author

From Chrome 66.0.3359.181 / 64-bit
500chrome

IE11
500ie

FF 59.0.2 / 32-bit
500ff

@mimckitt
Copy link
Contributor

@CKeene78 thanks for those. I think it would be best to get you in touch with a support engineer so they can debug the logs and see what is happening. Do you have the ability to open a technical Support ticket? If not I can enable one for you.

@mimckitt
Copy link
Contributor

I will close this out but if you feel you need more information please just let me know.

@onurtalayhan
Copy link

I have the same error. can you please explain how you solved it?

@PRMerger7 PRMerger7 added the Pri2 label May 22, 2020
@CKeene78
Copy link
Author

I had to create a route for the Reply URL.

Took me while to figure out that the requesting URL and reply URL cannot be the same! Had to add a route to receive the token, extract the token, and then call & supply the token to the original requesting URL.

  1. Requesting URL: https://funcsarc-msgraph.azurewebsites.net/api/ProfilePhotoAPICSharp2
  2. Reply URL: https://funcsarc-msgraph.azurewebsites.net/.auth/login/aad/[SOME ADDITIONAL ROUTES]
  3. Re-direct to Request URL with the TOKEN within the header or JSON body.
    ReplyURL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants