-
Notifications
You must be signed in to change notification settings - Fork 433
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
How to handle errors from SSO server? #921
Comments
So my first try would be first: Wrapping the promise in the APP_INITILIZER and catch the errors, then redirect the user or show an alert or something, or in the |
I have same issue my app crash when sso is down why? |
@mgamal-dev have you read my previous answer? |
Yeah, but I have some component will be public and not secured it is also crashed |
You have to wrap the promise and catch errors with a reject/resolve. Did not try it out but I think this should work. @VladislavOshkanov can you show me the configuration please? You have to make sure the app can start by catching the Promise and resolving it. Currently you can ask for the config and check for null. I have a PR which introduces an event if the authwellknown could not have been loaded.
|
Hi!
I need to handle errors from SSO server in my app, for example, if I got 404 on SSO url.
How can I handle this error in my app in order to prevent app from crash and show error message to user?
Thanks
The text was updated successfully, but these errors were encountered: