locked
Workflow of Authentication Federation with ASP.Net Identity in Web API and several mobile apps RRS feed

  • Question

  • User1259642964 posted

    Hi. I have implemented a Web API with ASP.Net Identity JWT Authentication to serve as a authentication server.

    Supposing i have several mobile apps consuming their own resource servers and each of them relying on the authentication server just for user registration/login/reset, i don't see a way of preventing having the same form for registration, login, password reset, on all mobile apps, even if the programming logic of the authentication is on the auth server.

    Could you tell me please nowdays how are the giants implementing this? Or even if you have any other suggestions of how the workflow could be?

    Thank you.

    Wednesday, April 6, 2016 6:00 PM

All replies

  • User614698185 posted

    Hi Don Quixote,

    i don't see a way of preventing having the same form for registration, login, password reset

    I am not sure your requirement. What's meaning of preventing having the same form for registration, login, password reset? Could you explain more?

    Best Regards,

    Candice Zhou

    Thursday, April 7, 2016 8:28 AM
  • User1259642964 posted

    Hello Candice. My goal is to do the same as i see on Web platform applications, where you have several web apps delegating authentication and registration to another web app which in turn will do the work. Google is an example, Microsoft another.

    In web environment, when you call google's login page from your web app you send the return url, so that google know where to send the token as parameter, if authentication conceeded.

    This is what i can't replicate on a mobile platform environment.

    Thursday, April 7, 2016 2:17 PM
  • User1259642964 posted

    Hello. Does anyone knows how to help me?

    Thursday, April 21, 2016 10:25 AM