Attaching to my version of the BSL hosted in Azure is failing

Question

Hi,

I am currently configuring my version of the Azure web applications to connect to my version of the Azure BSL.

I log into my Azure Stocktrader web site by going to ConfigWeb, demoadmin, password demo

then I untick Select from known

Then I type in my BSL config service url:

https://[my]stocktraderwebapp.cloudapp.net/config.svc

Select Client_ConfigSvc_BasicHttpBinding_T_Security

then click Login.

I then go to Connected Services and click Add Service

Type in Address to Configure Service: https://[my]stocktraderbsl.cloudapp.net:443/config.svc/

Then click Get Remote Services!

It connects.

The list shows:

Select from available remote endpoints: Azure BSL wsHttp security = Transport With Message Credential: UserName

Select Client Contract to use: Trade.BusinessServiceContract.ITradeServices

Select Client Configuration to use: Client_Ws2007HttpBinding_T_Security_MCredential_UserName_BSL

(I have also tried Client_Ws2007HttpBinding_T_Security_MCredential_ClientCert_BSL)

Online Check Method: isOnline

Online Check Params: None

Apply Default UserName Client Credentials is unchecked

The Choose Username for Default Client UserName Credentials... is Empty. Nothing there.

So

I tick the checkbox, but the drop down box is still not populated, and if I click on the Add button, it refuses to add the service:

The requested update was rejected based on the user authentication/rights check

Is there something I'm missing? Did I forget to add users in Azure or something?

Regards,

Tony

Answer 1

Hi Tony,

You need to login to ConfigWeb as "localadmin" (default password is "admin").  The "demoadmin" account is one that allows you to view, but not change, configurations.  So it looks like all is ok, follow the same steps, but always login as "localadmin".  You can also change your localadmin password from "admin" to a non-default secret password.  Think of the localadmin account as the 'sa' account on SQLServer/Mixed mode authentication--its always there and is the superadmin of the configuration service.

-Greg

---

Greg Leake, Microsoft

Answer 2

note when/if you change the 'localadmin' password, you will need to change to same value on the web app, bsl and ops if you want linked services in ConfigWeb to work.  Otherwise, you will still be able to login to individual configweb sessions against these services with their unique password, but not be able to navigate across services.

---

Greg Leake, Microsoft

Answer 3

Thanks Greg, I have now managed to get it working. It's looking great!