Improve DVLS server Microsoft authentication

Hello Marcel,

Thank you for your feedback. This is a great suggestion and we will look into it to see if we can make the page easier to follow.

Regards,

Hello again Marcel,

We've updated our documentation based on your suggestion.

Regards,

Hello @Emile Simard

Thank you for the update, which looks promising.
A few notes from my side.


Step 8 here is not very clear to me:
Is it to be repeated ? If so, in which case ? If not maybe it needs cleanup.
I think for Delegated rights, we need two different redirect URI's but I might be wrong.


This is not quite correct. If you do not add it here, the first user logging in will be required to do the Admin Consent.
I would rather add those manually, admin consent them and be done with it.


Instead of repeating 3 times "For Delegated permissions" I would add sub-steps for these 3 items and name the main step something like "For delegated permissions only do the following".


Thank you and best regards.
Marcel

Hi Marcel,

I have made the changes you requested. There was indeed a redundancy in step #8, as there is no need to input the redirect URI again, only the "ID tokens (used for implicit and hybrid flows)" checkbox is required for the application permissions configuration. I moved this instruction to step #7 instead, as it makes more sense.

For the "openid", "profile", and "offline_access" permissions, although they do not require admin consent by default, I have modified the box below step #15 for your use case. Thanks for bringing this to our attention, it may help others.

Regards,

Thanks @Emile Simard !
Let's see once we manage a successful delegated rights version if we need to URI's or not.
PS: For now, I can connect it, but not login to DVLS with it.
Marcel

Hello @Emile Simard

Tested: it needs both redirect URI's to work.


Otherwise I get this kind of response.


Cheers.
Marcel