I have just created a new project in VS2010 using the
Visual c# > Cloud > Windows Azure Project
template.
When I run it I would like to log in using the Admin account which I know exists in the secMembership table.
I assume there is a password published, but I can't find a reference to it anywhere. Am I missing some documentation somewhere or am I not concerned with this account?
Thanks
Are you talking about the Winodws 8 Toolkit? If so, try:
User Name: admin
Password: Passw0rd! (with a zero)
Otherwise the password may be just: password
If those don't work, try clicking on the ASP.NET Configuration button at the top of the solution explorer and click on the security tab. You should be able to create a new user or at least see if there is an admin account already. Chances are there isn't one yet.
Related
I am using below code to create CRM Client
var conn = new CrmServiceClient($#"AuthType=ClientSecret;url={organizationUri};ClientId={clientId};ClientSecret={clientSecret}");
Above code is throwing me "UserNotLicensed :User does not have license to use with access" error
I have also followed this article for creating application user. which is not possible as user needs to be created using power platform.
https://www.ashishvishwakarma.com/Dynamics-365-Single-Tenant-Server-2-Server-Authentication-Azure-Active-Directory-Access-Token/
Mine looks like
Also, as shown in the article I am not able to navigate to "New User" form. It keeps redirecting to Office Admin page. where I am not sure if I have permission to create. Let's say I make Admin do that, will Admin have option to associate User with application ?
creating application user. which is not possible as user needs to be
created using power platform.
what do you mean by this? You first need application user which should be created via Azure AD as app registration as mentioned in article and then you need to go to admin.powerplatfrom.com, select your env and then you see s2s users. Onye you click here it will give you list of all your s2s users (including the one you created). Add this s2s user in your env and assign particular security role (in most cases systemadmin). This should solve your issue
I'm starting a new project that will use ASP.NET Core Web App to login users using an AD domain.
When I try to add 'Work or School Accounts' with Azure AD authentication in VS I am greeted by this window. Could someone point me in the right direction where I need to look to solve this issue? Thanks!
When I try to connect to Dynamics 365 CRM with the Plugin Registration Tool I get the following permission error:
"You don't have permission to access any of the organizations in the
Microsoft Common Data Service region that you specified. If you're not
sure which region your organization resides in, choose "Don't know"
for the CDS region and try again. Otherwise check with your CDS
administrator. Parameter name: EMEA"
I have the System Administrator role
I can sign-in to the web interface and work with no issues
I'm sure of our region, tried to login with and without it ("Don't know" option)
Also tried with an application password as our organization uses multi factor authentication
Using the latest version of the tool on Nuget (9.0.0.9506 in the about dialog)
I can connect to my trial server the same way
We had a user who was able to connect with the same user roles set
This seems machine and account independent. Other users including the organization creator are getting the same error
We are directly connected to the internet, no proxies
One solution I've read suggested cleaning the cache files which don't appear on my system. And we get the same error on clean installations.
Solved by leaving the "Show Advanced" checkbox unchecked and not entering User ID / Password. Then a second dialog opens for credentials and 2FA authentication which just works.
You don't need an application password, as you'll be asked for MFA in the next step.
I don't know how our old teammate was able to sign in with the "Show Advanced" option selected. He was getting the same dialog and continue.
I was trying to create a project in visual studio, I chose the option Individual User Account after selecting WebApi project, and now in VS 2019 it seems to be pretty different than before, now some parameters are requested, can anybody give me some examples of how to configure it?
It is asking about:
Domain Name
Application ID
Sign-up or Sign-in Policy
And by default it is selected like the only option to select:
Connect to an existing user store in the cloud
That's because you are selected API project template and trying to set Individual User Accounts mode on that but WebAPI templates don't have the Store user account in-app feature.
If you're using MVC project and try to set the Authentication mode to Individual User Accounts you'll see the Store user accounts in-app option.
Also, you can try to start your project in the console with this command as said in this answer:
dotnet new webapi -au Individual
You can open your project in VS after that. (to work around the
dialog). Then you can use for example the authorize-attribute. But the
project is still configured to use Azure Bearer Authentication. You
have to decide where to get identity from. You can take
identityserver4 or build your own "Custom storage providers for
ASP.NET Core Identity" (MS-Docs)
This is because in MVC projects you have an account controller with
views to handle registrations and get a username and password and so
forth, but there's no such a thing in WebAPI and you have to use other
authentication mechanisms like JWT.
There's a discussion about this feature in AspNetCore's Github.
I am trying to add user having Hotmail account but team foundation showing following error.
Can anybody please tell me that how can I add another user in VSTS?
No identities found.
Depends on how your account was set up. If it's Microsoft Account based (LiveID/Outlook.com/Hotmail), then you need to navigate to the account level users hub first.
https://{{account}}.visualstudio.com/_admin/_users
If your account is Azure Active Directory backed, then you need to import these users into Azure Active Directory first, then add them at the account level before being able to add them to a security group.