Documentation is outdated about ms-identity-javascript-angular-tutorial

[derisen]

@nicostubi sorry for the confusion. The documentation you're looking at is for an app calling a web API (that's why it configures the protectedResources) whereas the folder 1-Authentication\2-sign-in-b2c contains just a sign-in sample. 3-Authorization-II\2-call-api-b2c\ folder contains the sample that calls a web API (as is mentioned in the documentation as well).

Again, apologies for the confusion. If you are ok with a web API in ASP.NET (as opposed to a Express web API as shown in the docs site), please just follow 3-Authorization-II/2-call-api-b2c

[nicostubi]

Thanks for clarifying. A web API in asp.net is even better. However I guess it’s only part of the solution, isn’t it? I am still seeing a mismatch between the documentation of the Angular SPA APP and the actual SPA sample in the repo. On 4 Jan 2023, at 19:41, Doğan Erişen ***@***.***> wrote: @nicostubi sorry for the confusion. The documentation you're looking at is for an app calling a web API (that's why it configures the protectedResources) whereas the folder 1-Authentication\2-sign-in-b2c contains just a sign-in sample. 3-Authorization-II\2-call-api-b2c\ folder contains the sample that calls a web API (as is mentioned in the documentation as well). Again, apologies for the confusion. If you are ok with a web API in ASP.NET (as opposed to a Express web API as shown in the docs site), please just follow 3-Authorization-II/2-call-api-b2c —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[derisen]

@nicostubi that's right, the doc site is still out of sync with the repo. For the moment you can just follow the README in the repo -I'll raise an issue on the doc site to let them know (but you are welcome to do this as well)

[nicostubi]

Thanks for the guidance, the swift replies and the samples Take care On 4 Jan 2023, at 22:14, Doğan Erişen ***@***.***> wrote: @nicostubi that's right, the doc site is still out of sync with the repo. For the moment you can just follow the README in the repo -I'll raise an issue on the doc site to let them know (but you are welcome to do this as well) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[derisen]

@nicostubi sounds great! I've notified the authors of the article. Closing this.