Fail - Connecting to Azure using application created in custom Active Directory

[rupert.br...@gmail.com]

I've installed the latest community edition of Scalr, and created a user account with which to connect to Azure.

Although I'm a global admin on the subscription the the Default Directory is inaccessible so I need to use a custom AAD called mytestdomain.onmicrosoft.com

Created a new application in the custom directory following the support notes https://scalr-wiki.atlassian.net/wiki/display/docs/Enabling+support+for+Azure

• Name : Scalr
• Sign on url : http://myscalrserver.westeurope.cloudapp.azure.com/public/xAzureToken (this is the URL used to connect to the admin console over port 80 - without the /public/xAzureToken)
• Application is multi tenant : yes
• User assignment required : no
• App id uri : http://mytestdomain.onmicrosoft.com/scalr
• Reply url : http://myscalrserver.westeurope.cloudapp.azure.com/public/xAzureToken
• Permissions delegated as per support doc.

Scalr-server.rb

• updated with client id and key from Azure application
• routing[:endpoint_host] = myscalrserver.westeurope.cloudapp.azure.com

Adding cloud credentials to an environment

Tenant Id: mytestdomain.onmicrosoft.com

Scalr logo appears, then pops up with error message : "Cannot proceed with your request. Try again later"

Any suggestions where I've made a mistake in the configuration? Or perhaps Scalr doesn't work with custom domains?

[ma...@scalr.com]

Hi Rupert,

After updating the scalr-server.rb file with your details as instructed by the documentation, did scalr-server-ctl reconfigure execute successfully? Were you able to login and attempt to configure Azure in one of your environments? Screenshots of your browser experience may be helpful.

[rupert.br...@gmail.com]

Hi Marc,

Yes I was able to log as admin, create another user, log on with the "regular" user and attempt to add cloud credentials.
Capture1.jpg shows an error that occured just after spinning up the VM (after having shut it down since yesterday) and trying to restablish the cloud credentials.
I delete the environment, create a new one and attempted to add the cloud creds again and got the error in capture2.jpg.

scalr-server-ctl reconfigure appears to execute successfully - there are no error messages at the end of configuration.
This is the output:

Running handlers:
Running handlers complete
Chef Client finished, 64/263 resources updated in 25.7266757 seconds

[Marc O'Brien]

Unfortunately that error message does not give much to go off of.  Assuming that there are no typos in any of your configuration, you may find better errors in the logs within /opt/scalr-server/var/log.

[rupert.br...@gmail.com]

Yes not very helpful were they :)

I provisioned a new subscription that uses our company Azure AD and got a different result. This time I can get to the point where I have to select a subscription but then get the error : "Azure Error. Bad Server response. Length required"

Looked at the logs. Tried saving the keys again and this time it worked. Not sure what the conclusion to draw from this is - don't use sub-domains maybe?

[Marc O'Brien]

Hi Rupert,

Very glad you were successful on your second attempt.  I had the same experience with the "Bad server response" but success on my second try today as well.

I will follow up internally regarding this behavior. 

Cheers,
Wm. Marc O'Brien
Scalr Technical Support

[Marc O'Brien]

2:45 PM (8 minutes ago)

Hi Rupert,

Quick follow up on this issue.  It turns out the error behavior we experienced was due to a change made by Microsoft on the Azure side.  The fix for this has been implemented in the latest Enterprise Edition of Scalr and will be included in a future update to Community Edition.  Keep in mind, access to the latest bug fixes and official support is a key benefit of upgrading to a hosted or Enterprise version of Scalr.  Just let us know if you run in to any issues in the future and we will do our best to support.

[Rupert Broad]

Ok great - thanks for the update. Appreciate you comments re support - I'm just doing research/investigation in to CMP solutions now. If/when we deploy to prod, it'll be a supported version.

cheers

--
You received this message because you are subscribed to a topic in the Google Groups "scalr-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scalr-discuss/Q1-PZlzVl8Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to scalr-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.