Reputation: 1415
Multiple apps, are under the same company, thus share users. Kinda like what Google does.
The apps have different databases, storages and resource schemes, therefore different requirements as for resource authorization.
The user can access apps using single singing, sharing the session.
I'm still at the designing stage. How should I approach it? Could it be that it simply comes down to writing different resource authorization attributes for each app?
Upvotes: 2
Views: 1293
Reputation: 115
You should use different databases, storages and resource schemes. Each app has its own unique name for connection. For example db connection name userdb, storage connection username struser... not use same password that accounts.
Upvotes: 1