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.

8
  • Why dont you use a role based access system. For example us users are member of "usUsers" and EU users are member of "euUsers" and then you handle access in your based on role membership. Commented Dec 6, 2019 at 12:12
  • yes thats what I am doing. The idp sends those usUsers and euUsers roles in the saml response and based on that I either disable USWebApp or EUWebApp buttons. However if they have access to both, then we need both apps and hence the question, should I need to write to 2 redis instances so when user clicks USWebApp, the USWebApp can validate with USRedis and when user clicks EUWebApp, EUWebApp can validate their session with EURedis. Commented Dec 6, 2019 at 14:38
  • Then i cant understand why you need a usWebApp and antoher euWebApp. Your app logic should handle the case where users have access to both regions. Or are you doing this because you are running your app in two different location? Commented Dec 6, 2019 at 21:00
  • Assume that those apps are not mine. they are maintained by other team for instance. All I maintain is the dashboard app. I save session to redis and send a cookie with redis id to respective apps and they should validate if this session is valid. However the question is should I store in two places since the apps that I might serve(EUWebApp or USWebApp in this case) maybe region based. Commented Dec 6, 2019 at 21:23
  • Then its not so easy to give a good answer. Need to know how these apps are handling the aurhentication, how this is stored in cookies and how its encrypted. Commented Dec 7, 2019 at 10:32