Exception | Solution |
---|---|
An existing connection was forcibly closed by the remote host | if you're IIS applicatin is running under and Application Pool that uses the identity of DOMAINNAME\domainuser, you would add this to the allowed client account list with the following command: Grant-CacheAllowedClientAccount DOMAINNAME\domainuser. [OR] use this Grant-CacheAllowedClientAccount everyone [OR] Set-CacheClusterSecurity -ProtectionLevel None -SecurityMode None |
Cache Configuration with Windows PowerShell | Reference |
Cache Administration with Windows PowerShell | Reference |
User Authentication in Multi-Tenant SaaS Apps Introduction We will cover few scenarios that we can follow to perform the user authentication in a Multi-Tenant SaaS application. Scenario 1 - Global Users Authentication with Tenancy and Tenant forwarding In this scheme, we have the SaaS Provider Authentication gateway that takes care of Authentication of the users by performing the following steps Tenant Identification User Authentication User Authorization Forwarding the user to the tenant application / tenant pages in the SaaS App This demands that the SaaS provider authentication gateway be a scalable microservice that can take care of the load across all tenants. The database partitioning (horizontal or other means) is left upto the SaaS provider Service. Scenario 2 - Global Tenant Identification and User Authentication forwarding In the above scenario, the tenant identification happens on part of the SaaS provider Tenant Identification gateway. Post which, the
Comments
Post a Comment