Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 2
    And don't forget to use https. You will need a digital cert. Commented Dec 8, 2016 at 20:02
  • 1
    +1 for HTTPS @Laiv. Edited. Commented Dec 9, 2016 at 0:57
  • 1
    @RikyTres that would help. I think you already know the OAuth2 protocol, but what worry you is not exactly the protocol itself. Looks like you are looking for a plan to make your environment scalable. Allowing new APIs or ClientsApp to consume your services. Am I right? Is it about the architecture plan? Commented Dec 10, 2016 at 18:30
  • 1
    Yep, you're right. I use OAuth to make scalable the AuthServer, and now i'm making a service that is a OAuth client. Now I need to make scalable also this service, and I create a server that expose a web GUI, and use the API of the OAuth client. Commented Dec 10, 2016 at 18:34
  • 1
    @linuxunil I think you should read the OP's edit and edit your answer too. You have introduced briefly concepts of web security and one of the possible flows for Oauth2, but questions turns around another subject. Commented Dec 10, 2016 at 20:10