You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to Microsoft, Windows Security should be used to provide proper security, unless there is a special need for integrated security. In case of DNN, this would require IIS App Pool user to be registered as SQL Server user and being mapped just to the database of the current site. This omits the need for providing username and password in plain text in DNN web.config (just using "integratedSecurity=true" option) and being limited for sure to the current database.
BTW: IMO it is easier to map the created user to the database instead of creating manually the database user and map to a login. Default schema should be "dbo".
Document Details
⚠ Do not edit this section. It is required for dnndocs.com ➟ Core Team processing.
According to Microsoft, Windows Security should be used to provide proper security, unless there is a special need for integrated security. In case of DNN, this would require IIS App Pool user to be registered as SQL Server user and being mapped just to the database of the current site. This omits the need for providing username and password in plain text in DNN web.config (just using "integratedSecurity=true" option) and being limited for sure to the current database.
BTW: IMO it is easier to map the created user to the database instead of creating manually the database user and map to a login. Default schema should be "dbo".
Document Details
⚠ Do not edit this section. It is required for dnndocs.com ➟ Core Team processing.
The text was updated successfully, but these errors were encountered: