Update the Azure AD App Registration's process guide

[magatz]

The registration process on Aif an app on Azure has changed so much that the guide is not so useful anymore.
I'm trying to figure out the new needed steps, and any help is welcome.

[jobec]

Azure did it again? They move so fast that it's hard to keep up with them.

Same with what they did in #67

My experience with Azure sadly is limited, but I'll see if I can figure it out (again) how to get an app registered.

If anyone reading this has more insight into what changed, feel free to open a MR to update the docs.

[dVerhees]

@magatz
I've actually managed to set it up with the latest Azure AD. The main difference is that when creating the web application registration you need to manually expose an API and select a scope for the API.
In addition the names have changed from WEB/API to just WEB application. and Native to Public client/native (mobile & desktop)

The api will also use a different url, like: api://application_id

I've used the following scope settings to get it to work:
Scope Name: Name for the scope
Who can consent? : Admins and users
Admin consent display name: This will show up if an admin logs in and needs to consent
Admin consent description: Same as above.

You won't normally see those consent messages as you'll use the "grant admin consent" option on the public client/native application registration.

@jobec I will probably be able to provide you with screenshots but I will need to blur all sensitive information so I don't know how helpful they will be.

[zdrouse]

Having some issues getting set up with Azure AD. Any update for changes to make with app registrations?

Been trying to follow the guide here but it looks a lot different on Azure side now.
https://django-auth-adfs.readthedocs.io/en/latest/azure_ad_config_guide.html

Additionally, it's not entirely clear to me why in Azure there are 2 app registrations needed for Web and Native. Would be helpful to better understand that part.

[jobec]

About the 2 registrations, that's because Django is acting as both "Client" and "Resource Server".
See here for more info: https://django-auth-adfs.readthedocs.io/en/latest/oauth2_explained.html

If I find dome time, I'll try to re-document the AzureAD stuff. But Like I said, they move so fast that it results in having to start from scratch every 6 months or so.

[gunflap]

@zdrouse @jobec @magatz @dVerhees I'm having some issues with Azure AD as well (django_auth_adfs Invalid issuer) - unsure if I'm setting things up correctly with Azure (since docs are outdated). Could you drop your photos/configuration (specifically AUTH_ADFS and your settings on Azure) for reference? Thank you.

[JonasKs]

#126 has been merged with updated docs for Azure AD! 🎉

As for how you set up a front end application (such as Vue or react) to speak with backend will come some time soon.

I'll keep this issue open until then.

[JonasKs]

This has been done.