-
Notifications
You must be signed in to change notification settings - Fork 218
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
[Bug] Blazor app Incremental consent issue #531
Comments
@sprakash10 can you provide a repro? is this w/blazor server or blazor web assembly? |
blazor server. |
that's not a repro, @sprakash10. We'd like you to provide repro steps, something like:
etc ... |
@jmprieur, Let me put the repo in GitHub. I will send you the link once done. Thanks |
Thanks @sprakash10 : that will be useful. |
@sprakash10 this has been address today. if you can pulling the master branch, you should see the issue resolved. I didn't realize this issue was related to this one |
@sprakash10, the fix is available in Microsoft.Identity.Web 1.0.0 |
Version: Latest
I am getting a different issue now. Flow is getting stuck in an infinite loop. I have verified all the code, it is the same as explained in the wiki. The browser keeps redirecting between given two URLs. I don't know what's wrong.
https://login.microsoftonline.com/common/reprocess?ctx=rQIIAY2TO4vjVgCF7fGMd3ZCyORB2CYwkC1C4I6vrKcHUkiWZEuy5Jc8lhyC0NtX1suWxg-lDymnDGkC2W5JmkAgbJV6YMkWYYu06bZKtkqRIrP_IM0HB86B03xnD8hL8hJewk8b7Ut49dh22w5kcAb4nQ4FCBhggKGDAGC-5-C43fYDF27eOzt_-e-Xr73Pn6vfvXr05Pf0t7-f1j9elmVeXLVaceba8TIryiuCwCm6VaAwRSnIkOf-Uq-_qNefHhUUTuME3sYJeE8Cdgj8chF5K40PK7NiS62nEtoUQrMS44EeHlTeLdVI2C_mKm7qAlSrMbnQJ7GaCPgiMkszkQ4muu_rZjWYi_GwJ5Warlamzh7M-SIe8gL2x9E7Q_amXLbfINugyn999DDINomV33_9tvHVcTfgZUYyNB8H4nRbatsJUqb-ULVZeZe7-0xkg5FjZSGaY9Us8BkCwGjFFeJeYuQtDxVOQiopWOzG2XDCtUla7LJ9E-6ExC2V-4UkxWvPFwyfw9fUWE5LCdsCfuoyirJIqO7EX2cTBAUAEwC6TBAPq9Uop5Uo62tsJWnCSJhHG07aGHZITQIb7DEoUXju2ga7olfGImUiLVd3xAxDq07ioNE85aby1gqdea6Nh7qxsnvWWInlfrqkPXN3SHKNXGqmWwlLMVgK3rzPuihJVsoU0QfAGjGkRAhC44ZRyYLD9wNxEHV3iO_ueijzunycbdPSWGIUfhBJsr0mFzxFdq_FHZcgNx4WBxNW1JQEa0fGhvtKHygYNuvpoAhvvHgip30MD_3ezgG7FV12CHhth6EyS6JEj1SB77MJd903tswEWKMVwoh1wbgyJngLah4YprXmJk7M95xq6tJIFg_0WrPd3Y2lxV3Ozpx2ZK490QAempJ8lHVX87jHg5npFInomVTaC8ephSpOsvKK1OWhS8-oZAq3458aTTdLkix91nhMY6TTwZ0AdDCCBEQAO8B2HRu4LkG4GN1xSDK4a3yU5X6KvIt8kwUo9i-yIIhR6lu26_pF8eK4_ur4w9OT85NHtYvaJx_AxtXp6dl57U3657j-_cm9TX--5RDPv-hyT2ovfyh__rF2d9LK2lILb6kKpmbwGivlWElEsT22MTNnenvSV_frohjYpbGFn2FX2G2zftts3jbfv2u-K_GWJuhTndV4dsK3LfhXs_71g9qzh_9H0W_O6r--XfsP0&sessionid=715b93bf-9145-4f09-acba-cc44c179b55f
https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=ac2b0838-e996-40f1-87ff-1edb33a2efc0&
redirect_uri=https%3A%2F%2Flocalhost%3A44367%2Fsignin-oidc&
response_type=code%20id_token&scope=openid%20profile%20offline_access&
response_mode=form_post&
nonce=637343235748506940.M2M0ZDljNTItODMyOC00NTlhLWIyMTctYWZhMWFmN2NlOGQ4NmYwODZkNGQtZGMyMC00MDI0LWI0ZWEtMWE2ZjA4OTcxNTI0&client_info=1&state=CfDJ8IXNe3-FSvtNvRiKSeOMaALGKoZ_JZExuzKvV40_28bAOSdaVOrQq82q4my1nYQ5gXd7pKSi7OJ9ZGXqAcQEi4DVi4HGN3PzFGHt1_a0yDtTeFSeru27ww-R54dvnYlLqWVMJ1i6akOD-Pa4m5iYFQWRhyFglmzwtmsbS0bjUfsgUZpHVV86pZDQLeHYLRTGdak3Z_mQ-b3wqplDqA09UmvXvWfFkwHCK18O3jSNmxpwEam10O3w2ENhiPDQjnrKdk-DOALPCoaimeNgpQpqPSKDq2_IuvmBos_mdLqFY41OCF0iX5XBhNEe9cBUWgqWF2MtvCJQ7FCRrlN-REfKE84dcm5rie13Rvbg7Qfg1UpxVGQbFJtpa-Dm233qt06DxHhtFMXaNmx21eEXQwBYLUzjrkffpUirHPArgKYNYWofeACuFJ1HN_armNO-3wVVyGL0pWjosZa0Wn5a-H_CyOPRU55Su0PEuXZIxRz3_uYuPS5DnGlVi1-xtKJ7zZ5b8g&x-client-SKU=ID_NETSTANDARD2_0&x-client-ver=5.5.0.0
The text was updated successfully, but these errors were encountered: