Badisi
Badisi
For anyone interested by a potential fix, have a look at my comment here: https://github.com/semantic-release/semantic-release/issues/2808#issuecomment-2407037933
@vzakharov-rxnt, 1. Make sure to use the `@angular-devkit/build-angular:application` builder so that **esbuild** is used 2. Build your Angular application with stats: `ng build --configuration=production --stats-json` 3. Reference that file when...
For anyone interested, the current workaround works for me: ```sh schematics .:hello --debug=false --name=paul --name=peter ``` _(tested with Angular CLI: 11.2.12)_
The [User](https://authts.github.io/oidc-client-ts/classes/User.html) object in `oidc-client-ts` has in fact a [profile](https://authts.github.io/oidc-client-ts/classes/User.html#profile) attribute which is: > "... a combination of the id_token and the user info endpoint" Provided that [loadUserInfo](https://authts.github.io/oidc-client-ts/interfaces/UserManagerSettings.html#loaduserinfo) setting is...
This is a NodeJS module. 1) Make sure you have [NodeJS](https://nodejs.org/en) installed on your machine (it will come with `npm` which is the package manager for node) 2) Create a...
I don't quite remember what was exactly needed for that. But I do remember having to set the `audience` in case of `Auth0` so that the `access_token` became a JWT....
Had the same issue today trying to set up my Jenkins pipeline. After digging, I found that the error comes from there: https://github.com/semantic-release/semantic-release/blob/45bf9d601591bf7649926e54a9459c643136b485/lib/verify.js#L14-L18 **Line 15** is swallowing the real error...
@ept-Ayush, I think you are approaching the problem from the wrong angle. Each web app should be registered individually in your IDP. They represent separated clients, and tokens from one...
If it's working for the majority but one, it means your config should be fine. For the one where it's not working, the problem is either the "user" or the...
While working in a local dev environment, `localhost` or `127.0.0.1` are usually considered **"secured"**. So using `http://localhost` as the redirect should be fine. You can also activate `https` with your...