question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Getting HttpErrorResponse after upgrading to 4.1.0 in my app with Azure B2C

See original GitHub issue

I haven’t changed any code in my app, just upgraded to 4.1.0 (from 4.0.3) and now I get this:

{
    "headers": {
        "normalizedNames": {},
        "lazyUpdate": null
    },
    "status": 200,
    "statusText": "OK",
    "url": "http://localhost:4200/api/oidc",
    "ok": false,
    "name": "HttpErrorResponse",
    "message": "Http failure during parsing for http://localhost:4200/api/oidc",
    "error": {
        "error": {},
        "text": "{"
    }
}

I wonder what has changed…

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
alvipeocommented, Mar 22, 2018

no, no, it works too. I just wanted to ask about this silent_renew_url and what to do with it?

1reaction
mcshizcommented, Mar 22, 2018

you should use the new silent_renew_url configuration. It’s at the very bottom of the docs here https://github.com/damienbod/angular-auth-oidc-client. Previously the silent renew Iframe was loading your entire application inside an iframe. Using this will prevent unnecessary side affects and reduce data-transfer

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error code reference - Azure AD B2C - Microsoft Learn
Error code Message Notes AADB2C90002 The CORS resource '' returned a 404 not found. Hosting the page cont... AADB2C90010 The request does not contain a...
Read more >
Azure B2C returning Status 400 (Bad request) when clicking ...
Azure B2C returning Status 400 (Bad request) when clicking Sign in button after tab is left open from night to day in the...
Read more >
azure ad b2c - User Flow - API connector cannot parse response
To troubleshoot the unexpected response, try sending Azure AD B2C logs to Application Insights. References: Azure B2C - REST API call Error.
Read more >
Azure AD B2C Tutorial: Authenticating In Sitecore Via Azure
Getting Azure AD B2C Ready to Go; Seconds Step: Preparing the Configuration; Third Step: Coding ... 4.1.0 NuGet package to your project,; Add...
Read more >
Add extra claims to an Azure B2C user flow using API ...
NET Core API application and the Azure API connector requests the ... The Azure API connector adds the claims after an Azure B2C...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found