Angular-auth-oidc-client: Master issue new version 11

[damienbod]

This is the master issue for planning the new release of version 11. Following features are planned:

• Refactor lib config to make it easier to use
• Update project to Angular 9 https://github.com/damienbod/angular-auth-oidc-client/issues/610
• add examples https://github.com/damienbod/angular-auth-oidc-client/issues/625
• support refresh tokens with example, and docs (coming safari change)
• refactor configuration property names
• eslint conform https://github.com/damienbod/angular-auth-oidc-client/issues/627
• Remove avoidable classes and add interfaces instead https://github.com/damienbod/angular-auth-oidc-client/issues/626
• Create Loglevel enum instead of boolean "isxyzactive" https://github.com/damienbod/angular-auth-oidc-client/issues/628
• Add prefix configuration for storage to allow multiple angular run in parallel https://github.com/damienbod/angular-auth-oidc-client/issues/634
• Add an event service with an enum to throw events out https://github.com/damienbod/angular-auth-oidc-client/issues/635
• Make folders for features not services, etc. #636
• SilentRenew breaks when using refresh_token and refresh_token is expired/invalid https://github.com/damienbod/angular-auth-oidc-client/issues/667
• Pack the tests beside the files which are being tested when feature folders are available #637
• support multiple instances in browser
• Do not provide default config when config should have been set before #644
• Code Verifier not cryptographically random https://github.com/damienbod/angular-auth-oidc-client/issues/642
• After successful login, getIsAuthorized still returns false for a bit. https://github.com/damienbod/angular-auth-oidc-client/issues/549
• Expose silent renew running observable https://github.com/damienbod/angular-auth-oidc-client/issues/447
• Issue with silent renew when js execution has been suspended https://github.com/damienbod/angular-auth-oidc-client/issues/605
• Add support for OAuth 2.0 Token Revocation https://github.com/damienbod/angular-auth-oidc-client/issues/673
• Silent renew dies if startRenew fails https://github.com/damienbod/angular-auth-oidc-client/issues/617
• support for Angular 8 , Angular 9
• redesign login init
• Remove avoidable anys https://github.com/damienbod/angular-auth-oidc-client/issues/624
• Use returned expired value of access token for expired validation
• Id_Token is rejected because of timing issue when server hour is different then client hour
  https://github.com/damienbod/angular-auth-oidc-client/issues/175
• fix validate, fix max time offset
• Support azp and multiple audiences https://github.com/damienbod/angular-auth-oidc-client/issues/582
• Add extra Refresh token validation https://github.com/damienbod/angular-auth-oidc-client/issues/687
• Notification that checking session is initialized https://github.com/damienbod/angular-auth-oidc-client/issues/686
• Refactor rxjs events, user profile events, silent renew, check session
• Add support for EC certificates https://github.com/damienbod/angular-auth-oidc-client/issues/645
• id_token : alg : HS256 support https://github.com/damienbod/angular-auth-oidc-client/issues/597
• redesign docs

In general the idea with this release is to make it easier to use, and improve the rxjs implementation.

Please comment here for improvement suggestions

[damienbod]

https://github.com/damienbod/angular-auth-oidc-client/issues/588

[inpicksys]

@damienbod Please. say - when approximately release planned?

[damienbod]

@inpicksys I guess it will take about 2 weeks, so when I start plus 2 weeks, kind of busy at the moment, and don't have time to start this yet.

[damienbod]

work for this will be merged in this branch

https://github.com/damienbod/angular-auth-oidc-client/tree/dev-version-11

[ntsehaye]

wondering when this release will be available? thanks

[damienbod]

Hi @ntsehaye very soon now, we have done most of the testing now, and all seems good. We just have the docs left now and then we will publish

[inpicksys]

@damienbod happy labor day!

[ntsehaye]

Hi @ntsehaye very soon now, we have done most of the testing now, and all seems good. We just have the docs left now and then we will publish

thank you for the update! appreciate it!