I creating a series about multi-tenants that use version 2 of the AuthP library - see the first one at bit.ly/multitenantPart1 . Note that the current video is still valid - version 2 just adds extra features.
Thank you very very much! It is very helpful! I did change the connection string to use SQL server instead of local DB and I got the following error A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) What can I do to resolve this? Thanks!
I haven't had this problem, but a quick Google of "The certificate chain was issued by an authority that is not trusted - try docs.microsoft.com/en-us/troubleshoot/sql/connect/error-message-when-you-connect
@@thereformedprogrammer Thanks for your quick response! I already tried this solution but it didn't work for me. I was working on Example3 and I just changed only the connection string and try to Update the Database using the ApplicationDbContext. Is there a way to remove the encryption? Thanks!
@@redietzewdu5349 Try Googling "The certificate chain was issued by an authority that is not trusted" and look at the other answers. Also the "Trusted_Connection=True" is used to log in to the SQL Server on windows. You might need to take that out and provide username + password of the SQL server.
I had this issue as well.... i added Encrypt=false onto the connection string and it resolved the issue. I can't say whether this is best practice or not, but it worked for me. Good luck!
1. Download the AuthP repro 2. Go to the Example3.MvcWebApp.IndividualAccounts project 3. Open the appsettings.json and make sure the DefaultConnection's server is set to to a local SQL Server server (I used localdb because many people have that) 4. Run the Example3.MvcWebApp.IndividualAccounts - this ASP.NET Core project is designed to create the database isn't there and seeds the database with demo data. 5. The Home page provides information on how to log in using the demo users.
!["Running SaaS multi-tenant applications on ASP.NET Core, Azure" Marco De Sanctis/.NET fwdays'23[eng]](http://i.ytimg.com/vi/gMH1fqA8wpw/mqdefault.jpg)
!["Running SaaS multi-tenant applications on ASP.NET Core, Azure" Marco De Sanctis/.NET fwdays'23[eng]](/img/tr.png)
This is great stuff! Right to the point and satisfies all the real-world needs. You are great jon
Glad you like it. Your might like this video th-cam.com/video/-sz49Qwjao8/w-d-xo.html which covers the new sharding feature
@@thereformedprogrammer Thanks, I have already seen this video and it was spectacular.
Fantastic work!
Please can you share this document/link.. I was looking your one of the article that you posted a few day back
I creating a series about multi-tenants that use version 2 of the AuthP library - see the first one at bit.ly/multitenantPart1 . Note that the current video is still valid - version 2 just adds extra features.
Thank you very very much! It is very helpful! I did change the connection string to use SQL server instead of local DB and I got the following error
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
What can I do to resolve this? Thanks!
I haven't had this problem, but a quick Google of "The certificate chain was issued by an authority that is not trusted - try docs.microsoft.com/en-us/troubleshoot/sql/connect/error-message-when-you-connect
@@thereformedprogrammer Thanks for your quick response! I already tried this solution but it didn't work for me.
I was working on Example3 and I just changed only the connection string and try to Update the Database using the ApplicationDbContext. Is there a way to remove the encryption? Thanks!
@@redietzewdu5349 Try Googling "The certificate chain was issued by an authority that is not trusted" and look at the other answers. Also the "Trusted_Connection=True" is used to log in to the SQL Server on windows. You might need to take that out and provide username + password of the SQL server.
I had this issue as well.... i added Encrypt=false onto the connection string and it resolved the issue. I can't say whether this is best practice or not, but it worked for me. Good luck!
Great job, thanks
This is magic thanks 😊
How to run project #3???
1. Download the AuthP repro
2. Go to the Example3.MvcWebApp.IndividualAccounts project
3. Open the appsettings.json and make sure the DefaultConnection's server is set to to a local SQL Server server (I used localdb because many people have that)
4. Run the Example3.MvcWebApp.IndividualAccounts - this ASP.NET Core project is designed to create the database isn't there and seeds the database with demo data.
5. The Home page provides information on how to log in using the demo users.
@@thereformedprogrammer Thanks is great !!!!