Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Function of Login Created from Asymmetric Key in External Access Assemblies? Expand / Collapse
Author
Message
Posted Wednesday, May 21, 2008 1:02 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:55 PM
Points: 1,863, Visits: 3,611
One of the ways of creating an EXTERNAL_ACCESS assembly is to:

(1) CREATE ASYMMETRIC KEY from the assembly dll;
(2) CREATE LOGIN FROM the ASYMMETRIC KEY;
(3) Grant EXTERNAL ACCESS ASSEMBLY permission to the LOGIN created in previous step;
(4) CREATE ASSEMBLY ... WITH permission_set = EXTERNAL_ACCESS;

I understand that an increased level of trust is required when external resources are accessed, hence the asymmetric key.

However, I don't see what the purpose of the LOGIN is.

In BOL (http://msdn.microsoft.com/en-us/library/ms189751.aspx) I read:
Logins created from certificates or asymmetric keys are used only for code signing. They cannot be used to connect to SQL Server.

Can someone please explain what that means?

What does this LOGIN actually do?!


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #504767
Posted Wednesday, May 21, 2008 7:18 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, June 5, 2014 10:54 AM
Points: 9,294, Visits: 9,480
I believe that you have to make the login the Owner (or executor?) of the Assembly

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #504935
Posted Thursday, May 22, 2008 7:42 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:55 PM
Points: 1,863, Visits: 3,611
rbarryyoung (5/21/2008)
I believe that you have to make the login the Owner (or executor?) of the Assembly


I did not have to make it owner of the assembly. But perhaps, as you say, it is the executor...

I just don't understand the BOL speak (see opening post).


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #505180
Posted Thursday, May 22, 2008 11:39 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, June 5, 2014 10:54 AM
Points: 9,294, Visits: 9,480
I agree, it's confusing. I am not sure what the answer is either.

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #505358
Posted Thursday, May 22, 2008 11:43 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:55 PM
Points: 1,863, Visits: 3,611
rbarryyoung (5/22/2008)
I agree, it's confusing. I am not sure what the answer is either.


No problem, thank you for responding.

I will be making the case for SQLCLR in an upcoming meeting, and I'm trying to fill up holes in my understanding (of which there are many! )


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #505362
Posted Thursday, May 22, 2008 3:43 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, June 5, 2014 10:54 AM
Points: 9,294, Visits: 9,480
As it happens, I was just working with a customer today on CLR assemblies, and it seems that the key/login is supposed to be used to "Sign" the assembly when it is built. The list that you have looks like it combines two different things: 1) creating an assembly that has been singed with a certificate or strong name(assymetric key), whose corresponding login has the EXTERNAL_ACCESS permission, as opposed to 2) Giving TRUSTWORTHY to the database and EXTERNAL_ACCESS permission to the database owner.


here is a microsoft link that explains: http://msdn.microsoft.com/en-us/library/ms345106.aspx


-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #505521
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse