joewalling / ReactAdvantage

SaaS starter kit with a React front-end with GraphQL
MIT License
22 stars 7 forks source link

Architecture based in ReactAdvantage #95

Open marcrib opened 5 years ago

marcrib commented 5 years ago

Correct me if I'm wrong

If I have more than one product, do I need to use a single server auth for all products? Would it be interesting to use this project as a basis?

I do not know if I was clear, I'll give an example

1 - Pharmacy Software 2 - Clinica Software

They are different business logic, so I would use ReactAdvantage as authserver

joewalling commented 5 years ago

Hi @marcrib The identity server is a separate project, that you should be able to use with both applications. However, if you want separate auth servers, you can do that as well.

If you build something based on this framework, I would love to see it and let others know about it.

marcrib commented 5 years ago

Hi @joewalling, thanks for awser

I'm studying the case. I think TenantId should only be added in the API resource using policyserver, leaving the IdentityServer only for general-purpose authentication

joewalling commented 5 years ago

Hi @marcrib, You are correct. I didn't realize my developer had not done it that way. I have him working on something else right now, but if you want to make the changes and submit a pull request, I'd be glad to incorporate it into the project. Otherwise, this will wait until one of my developers has some bench time to work on this.

joewalling commented 5 years ago

Hi @marcrib, did you decide to use this as a starter project? If so, did you make the changes? I have a developer free and was going to have him update the libraries and make this change if you have not already done so.