Azure AAD - works with some tweaking

[274188A]

@fretje - Azure AD Auth seems to be working - however I had to edit the existing record for the dbo.Tenant.Issuer after this warning appeared when running the API:

So after updating that record manually with the issuer value:

The WASM app ran ok and logged me in - :-)

PS: had to use a SPA platform configuration (web did not work for me) with a return URL of: https://localhost:5002/authentication/login-callback

[fretje]

Yes, that is something that still needs to be done manually... we could make it an applicationsetting "rootTenantIssuer" maybe? So you don't have to go diving into the database (for other tenants then the root tenant, you should be able to change it via the api/ui once that's implemented).

I have the client working as well... will do the docs soon... I see you've made yourself already quite familiar with it. If you would like to start the docs already, sure go ahead ;-)

I just don't know yet when I will find the time for it...

[274188A]

concerning the 'rootTenantIssuer' beng null - If you did add a new setting for the tenant, then it might be possible to set the 'Issuer' propertyy in the Seeding step?

My thoughts with the doc for this is not to spell out how to start from scratch with Azure - the user can find a ton of stuff in existing docs for setting up an App Registration.

So really the docs would be a few screens shots of the appSettings, Azure Apps with some commentary...

[PedroVentura235]

Hi, in this feature we will be able to use jwt + azure add simultaneously ? OR only one of them?

[fretje]

Only one of them. I don't really see the point. Or how you would distinguish between different authentication types at the api level. You choose how you protect your api be it using azure ad or that "home brewn jwt" (which I don't recomment btw) or maybe another way using auth0 for instance, and then you stick to it. You can't really choose 2 different ways to protect your api...

[PedroVentura235]

It was to have the possibility to login by azure, and by local only, for some users make mandatory by azure, and others could login by local