I was following the below link to setup the Azure AD B2C- with Graph API setup
https://azure.microsoft.com/en-in/documentation/articles/active-directory-b2c-devquickstarts-graph-dotnet/
I was able to proceed with powershell command settings, but when I try with the application, when it executes the below code,
authContext.AcquireToken("https://graph.windows.net", credential);
getting error like below, what is wrong with this ?
AADSTS70001: Application with identifier '33d8d9ba-8c07-462a-8936-23387ddb4x5e'
was not found in the directory abc.onmicrosoft.com
Trace ID: b858d725-fbaa-4a39-8da1-84ef2a82a0a9
Correlation ID: da7c254e-a10e-4df6-9965-215685447e74
Timestamp: 2016-03-29 06:40:23Z
How to resolve this. Any inputs appreciated.
Thanks for your comments, finally found the problem.
by executing the below command, found the application was not created.
Get-MsolServicePrincipal -AppPrincipalId 33d8d9ba-8c07-462a-8936-23387ddb4x5e.
I recreated the application and tried, things seems working.
I had an similar issue, this also got resolved
Error - Connect-MsolService : Your credentials could not be authenticated. Try again
If you have any problem creating the application on powershell, follow the solution provided in this below issue.
Several Azure AD. New-MsolServicePrincipal : Access Denied
Related
When i use the CallClient of #azure/communication-calling SDK to create a CallAgent, i'm getting 'No CommunicationTokenCredential provided' error even though i'm passing a valid CommunicationTokenCredential
Ex: this.callAgent = await this.callClient.createCallAgent(tokenCredential);
I'm able to successfully deploy a standalone react app & run the following sample application and make a web call as suggested in Microsoft docs. https://github.com/Azure-Samples/communication-services-web-calling-tutorial
But, when I integrate this into my existing React App, I start having issues in creating a CallAgent with the following error:
'azure:ACS:error 27/10/2021, 18:13:48:96 CallClient1:CallAgent1 op:Initialize failed, message=No CommunicationTokenCredential provided,'
I am passing the CommunicationTokenCredential properly while calling the createCallAgent(token) (verified by printing the token as well).
But still, I get this error. Has anyone else faced this issue?
Today, I'm not able to turn on debug on my ADFv2 mapping data flow. I'm getting the error below:
I already tried creating a new IR set to auto resolve and also set to same region as my ADFv2 - still no good.
Failed to setup debug session. Error: No connection is available to service this operation: SETEX dfProd_dataflowdebugsession26a9d381-5924-4c1f-b36f-cf41e2eab60e_f96ba068-97be-478a-8ed6-012a7ec58d80; IOCP: (Busy=0,Free=100,Min=50,Max=100), WORKER: (Busy=7,Free=93,Min=50,Max=100), Local-CPU: n/a
Congratulations that your error solved now.
I think maybe it's caused by the cache. Refresh the Data Factory and try again.
You tried again today and it worked.
I post this as the answer to make others know the error is gone.
What Azure Region is this factory in?
I'm trying to connect the SPGo plugin in Visual Studio Code to a Sharepoint Online site. There are lots of guides for this, for instance this one: https://medium.com/niftit-sharepoint-blog/saying-goodbye-to-sharepoint-designer-ac939a0b79ba
In short, I'm doing it like this:
Open VS Code
Open a local, empty folder)
SPGO: Configure workspace (follow guide, ending up with spgo.json
looking like the one I pasted)
SPGO: Populate local workspace (asking me for credentials and I plot
it in O365 style (email and password).
Statusbar says "Populating workspace"
After about 10 seconds I get the pasted error in the output window (spgo)
I'm using newest versions:
Visual Studio Code 1.37.1
SPGo 1.4.3
I have tried various sites in my tenant and I know they are up. I am Site Collection Administrator for the sites. I know the credentials are correct, of course. the remoteFolders and publishingScope doesn't affect anything, when changed. I assume authenticationType should be "Digest".
SPGo.json:
{
"sourceDirectory": "src",
"sharePointSiteUrl": "https://domain.sharepoint.com/sites/SiteName",
"publishingScope": "Major",
"authenticationType": "Digest",
"remoteFolders": [
"/SitePages/"
]
}
I don't get any files in the local folder, instead I get an error in the output:
================================ ERROR ================================
<s:Fault>
<s:Code>
<s:Value>s:Receiver</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="en-US">The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.</s:Text>
</s:Reason>
</s:Fault>
Error Detail:
----------------------
{}
===============================================================================
Sorry I missed this post for so long. First- thanks for the detailed write-up. This is the first time I've seen this specific issue with SPGo, so I do not know for sure what is the root cause.
Couple questions:
Are you using ADFS Authentication with your Office 365/SharePoint Online instance?
Are you able to use Addin-Only Authentication on this SP Site?
SPGo should be able to automatically work with ADFS in SharePoint Online but, as a fall-back, you could use Addin-Only Authentication. In this scenario you would create a ClientId and ClientSecret pair for the SharePoint Site Collection you are accessing and authenticate using those credentials. The ClientId would act as your UserName, and the ClientSecret would be your password.
Under the covers, I am using the node-sp-auth package for user authentication. Sergei (s-KaiNet on Github) has a great write-up on how to enable Addin-Only Authentication in SharePoint Online on his site, which you can find here.
Thanks for using SPGo!
I'm trying to deploy the mongo db quick start as seen here.
Unfortunately, it quickly fails with status CREATE_FAILED with the following error which I can't understand a lot from:
Embedded stack arn:aws:cloudformation:us-west-****** was not successfully created:
The following resource(s) failed to create:
[NAT1EIP, NAT2EIP, PublicSubnet1RouteTableAssociation, PrivateSubnet2ARouteTableAssociation, PublicSubnetRoute, PrivateSubnet1ARouteTableAssociation, PublicSubnet2RouteTableAssociation].
I tried using both my own user's role and a new role I created where the trusted entity was CF and permissions of power user. It failed in both cases.
I'm surely missing something very basic, any thoughts?
Thank you
If you are unable to create these networking resources, it could be very well due to IAM user restrictions.
I have been trying to use the library provided here, but I always get an error.
The command I am running:
GCUpload.exe -u:myUserName -p:myPassword -n:myProjectName -s:Test -f:myFile
but I get the error of:
That's an error. Your client does not have the permission to get URL /files from this server.
(Client IP address: <My IP address>)
Please sign in to upload a file.
I can log in to google code with the user and the project exists. What am I doing wrong and how can I solve this issue? Thanks.
EDIT: Maybe some credentials must be provided, but I'm not sure what is needed. I've tried this command without success:
net use \\code.google.com\projectname /user:username password
The error is:
The network path was not found.
The problem was that I have run the command with my google user's password, but there is a separate Google Code password which can be found here, but you have to be logged in to see it.