web service suggestions

Question

0.00/5 (No votes)

See more:

We have one main site, database and we have got two different apps developed by external companies.

Now we have a user database in our main site. Now for these apps, one company suggesting us to create a web service that they can call and find out in true/false if user is a member or not.

The second company is suggesting they will have a separate user database and create a REST API calls that our system can interact with. So we need to create a service that updates the app database.

Now am thinking may be it's best to stick to one solution for both rather than different solution. I am more incline towards first suggestion?

What do you all think?

Thanks

Posted 7-Jan-14 1:17am

AndyInUK

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

db7uk · Answer 1 · 2014-01-07T01:53:00

The second suggestion is not really that good as it adds quite a bit more work and risk.

Sometimes the simpler methods such as point 1 are probably good to go with. As with any security concern this will / should dictate the requirements. Having a separate database does add some benefit but would be more problematic.

I would go for point 1.

However, Have you looked into Windows Identity Foundation? It uses federated security whereby you could have multiple applications all signing on using a single user token. This is claims based authentication and would work quite well in multiple applications scenarios

http://msdn.microsoft.com/en-us/library/hh377151(v=vs.110).aspx[^]