Badisi

That would work because `session_state` is unique and thus identical for each tabs. But it would work only for Keycloak (at least) because there is no such info returned by...

The more I think about it, the more I realize it should be an issue on Keycloak side. Auth0 reasoning (see [Automatic-Reuse-Detection](https://auth0.com/blog/securing-single-page-applications-with-refresh-token-rotation/#Automatic-Reuse-Detection)) seems way more logical. They invalidates the RT...

@DASPRiD , as I explained [here](https://github.com/authts/oidc-client-ts/pull/434#issuecomment-1077813953), using the `refresh token` as a lock key would be useless because each browser tabs receives a different refresh token. To me the only...

~~It might help summarizing a bit because this discussion is quite long :)~~ ~~_(so correct me if I'm wrong or if something is missing)_~~ ~~Pending required changes:~~ ~~- [ ]...

~You should be able to do it with your own Navigator implementation.~ ~You can have a look at [PopupNavigator](https://github.com/authts/oidc-client-ts/blob/1d8254343748c367ef46e0992c510759ece990a2/src/navigators/PopupNavigator.ts) and [UserManager.signinPopup](https://github.com/authts/oidc-client-ts/blob/12024b48738cde94de48ea37252f02811534f531/src/UserManager.ts#L177) to see how it's done for the popup mode.~...

Yes, code for the custom url scheme callback is: [here](https://github.com/Badisi/auth-js/blob/main/projects/auth-js/oidc/oidc-auth-manager.ts#L439)

Thanks @brockallen ! I didn't know about that. https://openid.net/certification/fees > Member Certification Fees > $700.00 USD per new deployment > > Non-Member Certification Fees > $3500.00 USD per new deployment...

As per your log, the issue resides in `[email protected]` (not `@jscutlery/cypress-angular`). Tree : `@jscutlery/cypress-angular` -> resolves to `0.5.1` -> **dep**: `@jscutlery/cypress-mount@^0.x` -> resolves to `0.10.1` ---> **dep**: `ng-dynamic-component@^0.8.1`-> resolves to...

**EDIT**: I think the best recommendation is to use `"version": "0.0.0-semantically-released"` as you do. It is self-explanatory and it avoids the issue below. --- #### Issue Consider the following: -...

I don't think this is related to your update as the error here comes from the `normalize-package-data` package. It simply does not accept `"*"` as a version. But anyhow it...