Ng16 migration #10114
Merged
Ng16 migration #10114
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VitoAlbano
requested review from
DenysVuika,
eromano and
popovicsandras
as code owners
wojd0
approved these changes
Aug 22, 2024
VitoAlbano
force-pushed
the
ng16-migration
branch
4 times, most recently
from
779e2f3 to
3afbfe1
Compare
VitoAlbano
force-pushed
the
ng16-migration
branch
from
3afbfe1 to
4124efd
Compare
VitoAlbano
force-pushed
the
ng16-migration
branch
from
d26f60a to
fd74a09
Compare
dominikiwanekhyland
force-pushed
the
ng16-migration
branch
from
b72786d to
30fda69
Compare
VitoAlbano
force-pushed
the
ng16-migration
branch
8 times, most recently
from
bab6fe9 to
b01faa3
Compare
|
Please retry analysis of this Pull-Request directly on SonarCloud |
DenysVuika
reviewed
Sep 10, 2024
DenysVuika
reviewed
Sep 10, 2024
DenysVuika
reviewed
Sep 10, 2024
DenysVuika
reviewed
Sep 10, 2024
VitoAlbano
force-pushed
the
ng16-migration
branch
3 times, most recently
from
ce5eef3 to
dace3aa
Compare
…moved from a node (#10285)
…10272) * AAE-26163 Logout user after 3 login attempts failed, avoiding infinite loop when an authentication error occured, like when a user machine clock is significantly out of sync * AAE-26163 Wait to discovery document to be loaded and user not authenticated to perform a ssoLogin, logout user if login fails after 3 attempts * AAE-26163 Fix missed id_token_hint invoking logout when a login error occured due to a clock significantly out of sync * AAE-26163 Add fake observable to unit test * AAE-26163 Show oauth event logs if showDebugInformation is enabled, remove auth items if access token is not valid * AAE-26163 Improve tryLogin error message * AAE-26163 Check if token has expired to fix case when user access the application after the token is expired and with a clock significantly out of sync * AAE-26163 Test logout when clock is out of sync * AAE-26163 Create a service to check if local machine time is out of sync * AAE-26163 Update oauthErrorEvent$ and combinedOAuthErrorsStream$ to return errors * AAE-26163 Output error within combined oauth error event subscription * AAE-26163 Fix lint problems * AAE-26163 Logout user when token refresh error happens for the second time, if the token is not refreshed properly after first refresh error * AAE-26163 Logout user once an oauth error event occur due to clock out of sync * AAE-26163 Fix retry login error message if the OAuthErrorEvent doesn t return reason * AAE-26163 Fix the issue where the logout API call is canceled by the authorize call when login fails due to clock synchronization problems, causing an infinite loop. * remove console.log * AAE-26163 Fix retry login error message if the OAuthErrorEvent reason is an empty object
VitoAlbano
force-pushed
the
ng16-migration
branch
from
0232d53 to
338d3bb
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: