Timeline for SQL Hardening, BCS, and ECT (SharePoint 2010)
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2011 at 22:27 | comment | added | Erik M | Thanks Lori, we have decided to use the Secure Store Services with an SQL account, instead of changing up how our domain is currently configured. SQL authentication passes all information encrypted so I think this will do the trick. | |
| Oct 25, 2011 at 21:25 | comment | added | Lori | That is very possible. You might consider using authentication with the application pool ID "revert to self" for SQL and granting or removing permissions to the ECT in the Business Data Connectivity Service and through the External list permissions. This could bypass this issue. | |
| Oct 25, 2011 at 21:02 | comment | added | Erik M | I am trying to access it within an Intranet site, we have 2 domains setup. I think we have pin pointed it to being related to that as when my co-worker or myself login we get the "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'." message, and my other co-worker will be allowed access(once granted on the database) since his username is on the proper domain the servers are on. | |
| Oct 25, 2011 at 20:20 | comment | added | Lori | Are you trying to access this from an anonymous public facing site? I have had this problem with those sites, and you have to use revert to self and a data view web part to truly reveal external content anonmyously. I have a link for instructions on this if this is the case. | |
| Oct 25, 2011 at 19:43 | comment | added | Erik M | I have been able to successfully connect with the SSS through using a SQL account after configuring in SPD with the proper aliased server name (case-sensitive). I am now getting a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'." message when using "Users Identity" for authentication. I have full permissions to the database (note this is with using the aliased server name). The SQL server has been configured to use just Windows authentication. | |
| Oct 25, 2011 at 18:37 | history | answered | Lori | CC BY-SA 3.0 |