My cluster is using Windows Authentication for client to endpoint and it works as expected in browser when connecting to cluster by prompting to use username/password to connect to SF console.
I'm confused as far as what I'm supposed to put into publish profile in Visual Studio. There is no option to choose Windows Authentication anywhere, only cert and Azure Active Directory. How is it supposed to work?
Using WindowsCredential="True" in the publish profile should work. Here is a powershell version that has worked for me in the past.
Connect-ServiceFabricCluster -ConnectionEndpoint:':19000' -WindowsCredential:$true -TimeoutSec:60
Related
I have installed several application on a BizTalk 2020 server using BTDF 5.8 where I used to the application settings in the deployment to update any config for the BizTalk applications.
My own account is part of the SSO admin group and I use the in proc host account to install the apps into the BizTalk server. The proc host account is also part of the SSO admin group.
When I view the SSO using the admin or client utility no apps are shown. I also downloaded and run the BizTalk-Server-SSO-Application-Configuration-Tool. The tool also showed no current installed applications, but was able to add an application with it config.
But ideally I would like to view and edit current config as I am currently getting an error on a server with incorrect value.
Is there another tool to view and edit settings or am I missing something that must be enabled.
I just installed Azure Devops 2019 on my server. I can access the devops server fine through the web portal but when I try to connect using VS 2019 - team explorer - manage connections - Add Azure Devops Server I get a error "TF400324: Azure DevOps Service are not available from server http://xx.xx.xx.xx:8080/tfs."
I also see that VS add :8080/tfs to the IP I add. But thats not the correct adress. When using Team Foundation Server this adress was valid but Azure Devops does not use the same.
So how can I connect to the new Azure DevOps server from VS 2019?
So how can I connect to the new Azure DevOps server from VS 2019?
You can try:
1.Close all VS instances and then clean VS cache(%LocalAppData%\Microsoft\VisualStudio\16.xxx\ComponentModelCache) and TFS cache(%LocalAppData%\Microsoft\Team Foundation\xx\Cache).
2.Go to Control Panel -> User Accounts -> Manage your Credential -> Windows Credential, select the VSTS url to remove it.
3.Restart VS to re-connect to Devops server.
In addition:
1.Make sure you enter the correct URL. In VS if I don't enter correct URL of tfs instance, I would get this error:
2.Many factors can cause TF400324, just like above. So it could be better if you can share more details about your TF400324, remote name not resolve,Could not create SSL/TLS secure channel or what.
I had issues connecting to DevOps. I was using https and http. The trick for me was to "Change Public URL" in the "Azure DevOps Server Administration Console". This was done on the "Application Tier". Once I had this done the redirect for HTTPS worked because it used a fully qualified DNS name that matched the certificate I was using.
If you are not using HTTPS, then you may just have a DNS server issue. Check the DNS settings on the client PC and use something like ping or nslookup to see if the server name resolves to the correct IP address.
I have installed CF on virtualbox using BOSH. Now I would like to use CF CLI and install an application on CF. For that, I am following instructions here: https://github.com/cloudfoundry/cf-deployment/blob/master/deployment-guide.md
It suggests to run "credhub login" and get the CF credentials to log in to CF. However, credhub login does not work. It doesn't identify the credhub command. My understanding is that credhub gets installed along with CF during deployment process which doesn't seem to be the case.
I am wondering how do i fetch the admin password for Cloud Foundry that I just installed on a virtualbox using bosh as credhub doesn't seem to work.
I also don't see a password for CF in credhub.yml in bosh-deployment folder.
I am not sure how this works. Any help would be highly appreciated.
Working in a Debain 8 vagrant box and I'm trying to connect to the gcloud, but I'm unable to authenticate through a webapp cause there is none. Anyone know how to get authentication?
You could use gcloud CLI tool (here). Install it, run gcloud auth login and it will display a link you can open on a different machine to authenticate and paste back a secret to the machine where you ran the command to get authentication there.
I have been trying to install the Azure Active Directory Module for Windows for Powershell. So far I have not been able to find a combination of the Sign-In Assistant and Powershell module versions that allows me to create a connection in a Powershell session. My measure for success has been to run the Connect-MsolService cmdlet to create such a connection. I have tried it both from the command line and in a script. The (few) forum and blogs posts that reference this functionality have been very contradictory.
I am using the same credentials that I use to log into manage.windowsazure.com.
As to the specifics I have the following configuration:
Windows Server 2012R2
Powershell version 4.0 ($PSVersionTable.PSVersion)
Microsoft Online Services Sign-In Assistant version 7.250.4556.0
Windows Azure Active Directory Module for Windows Azure version
1.0.8362. The version number is based on the command (get-item C:\Windows\System32\WindowsPowerShell\v1.0\Modules\MSOnline\Microsoft.Online.Administration.Automation.PSModule.dll).VersionInfo.FileVersion
My questions are as follows:
What versions work on Windows Server 2012R2?
Is there a specific .Net version that I might be missing?
Am I looking at it wrong? For example is the cmdlet
Connect-MsolService not the metric to be using? Is there another way
that I might verify that I have a connection?
My understanding is that the Powershell cmdlets, as well as all the other methods for managing Azure, are based on the REST API's. Would that be a better way to go? Of course I would not be able to dynamically enter commands, but I would be able to validate credentials etc.
Are you trying to authenicate with an MSA account? Try connecting with a Global Admin AAD account (eg. globaladminuser#tenant.onmicrosoft.com).