It is work!   i added policy config to the json file and succeeded in creating the cluster    The contents added to the json file are as follows   Think you! "Effect": "Allow", "Action": [ "iam:ListRolePolicies", "iam:GetRolePolicy", "iam:ListAttachedRolePolicies", "iam:ListInstanceProfiles", "iam:PutRolePolicy", "iam:PassRole", "iam:GetRole", "iam:CreateServiceLinkedRole" ], "Resource": [ "*" ] ... View more

I have faced similar issue. When I try to logon to KnoxSSO, it is authenticated correctly and redirected to SSO logon page. After few hours investigation, I have realised that I need to setup ldap configs for my Advanced topology in Knox too. Not just KnoxSSO. I made below changes and I am able to resolve the issue.   Under Advanced Topology <param> <name>main.ldapRealm.userDnTemplate</name> <value>uid={0},cn=users,cn=accounts,dc=us-west-1,dc=compute,dc=internal</value> </param> <param> <name>main.ldapRealm.contextFactory.url</name> <value>ldap://xxxxxxxxxxx.us-west-1.compute.internal:389</value> </param>   Under Advanced knoxsso-topology   <param> <name>main.ldapRealm.userDnTemplate</name> <value>uid={0},cn=users,cn=accounts,dc=us-west-1,dc=compute,dc=internal</value> </param> <param> <name>main.ldapRealm.contextFactory.url</name> <value>ldap://xxxxxxxxxxx.us-west-1.compute.internal:389</value> </param> <param> <name>knoxsso.redirect.whitelist.regex</name> <value>.*</value> </param> And I have ensured the Ambari LDAP setup has the same basedn      ... View more

Thanks! This solved the issue. Once I had removed the SQL service endpoint from the VNet that hosted my cloudbreak VM everything worked fine 🙂 ... View more

@pdarvasi I was following the instruction provided by Hortonworks: Launch Cloudbreak - Cloudbreak on Azure Marketplace But with link provide by you, I was able to create cloudbreak 2.7.0. Thank you. ... View more

Hi @Marshal Tito, unfortunately there is no option from 2.0 to 2.7 (latest at that time) to organize roles and accounts. You have two options: Wait for the feature which is on the way Use 1.16.x until the feature arrives in version 2 ... View more

@Airawat If you consider your original question answered, would you please consider accepting the answer? Thanks! ... View more

@pdarvasi Thanks! ... View more

@Anagha Khanolkar Feature timing-wise, unfortunately I cannot make any statements so you should contact the sales or solution engineer contact of your customer. ... View more

@Farrukh Munir If you think your original question was answered, would you consider accepting it? Thank you! ... View more