authentication through externals app (android or dot net) to D365 Finance and operation to use Odata and custom service

(0) Share

Report

Posted on by MinaSafwat

Dear All,

I have a question regarding authentication through externals app (android or dot net) to call ODATA, we registered the app in azure active directory and add teh permission and get the client and secrets key and also bind a user with client ID with User in Dynamics FO 356, however we have the following question:

1- Should we add a new app registration for every users using the external application , so imagine we have 10 users using the same (dotnet or android app), does that mean we have to add 10 app registration in Azure active directory and add different the client Id and secert ID for each user?

2- Can we use the normal username and password to do the authentication instead of the client ID and Secert ID as they are not user friendly.

Thanks,

Mina.

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Suggested answer

nmaenpaa 101,172 Moderator on at

Like (1)

Report
Copy link

Link copied!

You don't need to use app id and secret, instead users can also login with their O365/AAD accounts (username and password) . And they can all use one and same app id (AAD app registration is needed anyway).

Was this reply helpful? Yes No
MinaSafwat 40 on at

Like (0)

Report
Copy link

Link copied!

Hello Nikolaos,

Thanks for your reply.

Where could I find Dotnet library and Android library to do that?

Thanks,

Mina.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

You can search the web for MSAL library for different platforms.

Was this reply helpful? Yes No
MinaSafwat 40 on at

Like (0)

Report
Copy link

Link copied!

Ok I will search for that.

but in case we will use the client Id and secret, then we will need t add app registration for every users logging to the application (like if we have 100 user accessing the android app then will need to add 100 app registrations, and each with different client Id and secret Id), is that correct.

Thanks,

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,172 Moderator on at

Like (1)

Report
Copy link

Link copied!

100 users can use same client id and secret. But then you can't use it to manage identities, only for authenticating the connection as "service account".

For example Microsoft's own Warehouse mobile app uses client id+secret, or alternatively a certificate for authentication. Additionally users type some simple user id and password (which are maintainedd inside Dynamics) to login. This way each user is still identified separately even though their connection to D365 is authenticated with one secret/certificate.

docs.microsoft.com/.../install-configure-warehousing-app

Was this reply helpful? Yes No
MinaSafwat 40 on at

Like (0)

Report
Copy link

Link copied!

I am a little bit confused, i think still in our case as we haven't userID for worker, if we need to manage identities, we have to add 100 app registration in azure

or use MSAL, authentication?

is it correct?

BTW i tried to add user ID to worker but I can't find the default warehouse (it is empty although there is defined warehouse in the system), what should i do?.

Thanks,

Mina,

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,172 Moderator on at

Like (0)

Report
Copy link

Link copied!

I'm not sure if I understand your question.

I have described the options, but I can't tell what you should do. This is part of your technical architecture for the app. Current IT landscape and architecture of the customer, business requirements and many other things need to be considered. But perhaps the core question is: "Should the app users be able to login with their O365 credentials or not?" If yes, then they should be added to D365 users, and use their own credentials. If not, then you use app id + secret, and need some other way to distinguish the identities of different users.

But managing 100 app ids and secrets doesn't necessarily sound like the best solution.

Was this reply helpful? Yes No