Quantcast
Channel: Service Bus forum
Viewing all articles
Browse latest Browse all 1916

How do you create a SaS Connection using SB 1.1 Preview without using Azure Portal Pack?

$
0
0

I have the Connection String setup:

Endpoint=sb://<machineName>/<namespace>;StsEndpoint=https://<machineName>:9355/<namespace>;RuntimePort=9354;ManagementPort=9355;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<password>

First off, I have no way to find out what is the Token Passcode it created for RootManageSharedAccessKey. According to article "http://msdn.microsoft.com/en-us/library/windowsazure/dn170477.aspx" it says the following:

When a Service Bus namespace is provisioned, a SharedAccessAuthorizationRule, with KeyNameset to RootManageSharedAccessKey, is created by default. 

I want to use a SaS Key/KeyName at the Namespace level, not the individual Queue/Topic level.

This leads me to believe that this key name is automatically generated when you provision a new namespace in Service Bus. However, there are no Powershell commands to view this. You can see the PrimarySymetricKey, but that is not the key you need for that. I know I tried, that is used for the namespace setting. I tried to utilize the rest endpoint on the server to maybe see the autorization rule, but get no response from this (the long string is 0's is the subscription Id I get back from Powershell):

https://<serverName>/00000000000000000000000000000000/services/ServiceBus/namespaces/<namespace>/AuthorizationRules/

I need help. Is there any way to do a SaS connection without having to use Active Directory for the token? I thought that was the new feature of SB 1.1, was to utilize SaS rules. Again, I do not want to create a SaS Key/Keyname at the Queue/Topic level, I want to create it at the Namespace level to allow me to create queues, etc through code with manage privileges without having to utilize a AD account.


Viewing all articles
Browse latest Browse all 1916

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>