security - Separate authentication server for users and APIs -


i'm working on cloud service authentication system , i'm not entirely sure optimal way handle authenticating requests is. we're planning run our image server separate process our api server can scale them independently of each other. handling request authentication api keys simple, because can have image server store own api key , check requests provide in header (over https obviously), same api server. users though gets more complex.

right have setup api server handle generating session token , storing users in database, we'd use 3 servers:

  • authentication server
  • api server
  • image server

and have image , api servers authenticate requests against authentication server. how should done though? seems bad idea performance-wise hit authentication server every request api , image servers make. can/should token verified different server created on?

so example: can/should pass token received authentication server image server, verify token came "my.auth.server" , check user id right one? jwts type of token this?


Comments

Popular posts from this blog

java - Jasper subreport showing only one entry from the JSON data source when embedded in the Title band -

mapreduce - Resource manager does not transit to active state from standby -

serialization - Convert Any type in scala to Array[Byte] and back -