UserNotLicensed :User does not have license to use <ModernProject> with <ReadOnly> access - dynamics-crm

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

Related

How can I easily add others to update my G Suite App listing?

I've looked all over the admin console, but can't find where to add other users so that they can edit our listing. Can you please provide a URL/link to where I should navigate?
You may want to check this support page. You can:
assign pre-built roles for performing common business tasks
assign custom roles you create for your organization
assign more than one role to a user to grant all privileges in those roles
Be noted that you must be signed in as a super administrator for this task.
The user typically gets their new privileges within a few minutes. However, it can take up to 24 hours. When they sign in to their account, they arrive at the Admin console dashboard. Here they see the controls allowed by their privileges.
Hope this helps!
I think you want to navigate to this URL while logged in as the app project owner:
https://console.cloud.google.com/iam-admin/iam/project?project=(add your project ID)
And assign roles to different users or groups.
you can use group publishing on the gsuite marketplace:
Set up Group Publishing
You can share ownership of your items in Google Chrome Web Store with other developers by setting up group publishing. With group publishing, you can add developers to a Google Group, who can then act on your behalf. They'll have access to all the items you own and can make any changes to them that you can make.
https://developer.chrome.com/webstore/publish#set-up-group-publishing
(each member of the group should pay the 5$ developer fee though.)
You can configure the group from your webstore dashboard.
https://chrome.google.com/webstore/developer/dashboard

Windows store app certification failed - New user sign up for services missing

Our windows store application is especially for our customers.
It requires user credential to login.
It doesn't have any sign up page.
New users cannot access our application(They should be our customer.)
For new users, Admin will create an account and share them to the
user.
At the first time, user is requested to change password.
This is how our customer access our application
We submitted our free business app to the windows store.
But it is rejected with the reason saying "Apps that require users to sign in must either specify upfront in app description the type of access user must have and how to get it or provide a mechanism for new users to sign up for services from within the app. At a minimum this could be a link in the app to the website where the user can create a new account and sign up for services. Your app did not appear to provide this information to the user."
We do not have such a page. How can we proceed for resubmission?
Whether we need to provide description like "Our application can be accessible to our customers only"
or
provide support email address and saying like "Contact our support team/admin to create new account"
or
any suggestions?
Simply show a description which tells user that this app is only for registered customers. For more details you can write us to your email id or can fully describe the log in process there on the first page.
The description says it all. Include exactly what you have said in the application's description update. In addition include this information on the main page of your application for extra safety.
Note how DropBox has done it. When you install the app your very first screen has the login boxes and a link to "or Create an Account" which then brings you to a webpage to create the account.
You could link this to a page on your site that allows a user to contact your org for an account or register for one to then be approved, etc

Is there anything I can use to mock an AD API for getting a list of users?

I don't need AD for anything more than getting a list of user names. My application uses it's own, custom auth, but it does checks based on the domain username of the logged on user, so the user names in my Users table should match those used by the logged on users.
E.g. For domain user johnblack to access features in my app, the app admin must create a user in my app called johnblack, but when creating this user, the username is a free text field. This allows the app admin to mistakenly create a user called jonblack. I want to make the user name field a dropdown, populated with users from the domain, when the admin adds a new user.
However, the epic saga involved in getting AD running on a VM on my Win 7 Home laptop is just too much overhead for now. Are their any mocks I could use, where my C# code needn't change to switch over to real AD?
Have a look at Active Directory Lightweight Directory Services (AD LDS) - formerly also know as AD/AM (AD Application Mode).
http://msdn.microsoft.com/en-us/library/windows/desktop/aa705886%28v=vs.85%29.aspx
It's a lightweight version of AD, which smells like AD, behaves like AD, but it's a NT service that you can start (and stop) at will, and it doesn't completely take over your machine/server - you can easily disable/uninstall it.

How to configure user for worklist application and human workflow?

I am new in SOA Suite and we are using SOA suite 11g. Please let me know how to configure user for human work flow and work-list application. I created simple users in weblogic realm. but how to set which user can be administrator or which user will be end user.
please refer some documents also.
Hi, thanks for suggesting, but I am so much confused. when creating a task in BPEL application we need to provider user information in assiginment tab. so here only those users listed they are in weblogic realm. but while creating user in weblogic I am not getting any option for making this user as administrator or end user. right now i have created user in weblogic and when I am creating task its getting in inbox of particular user also. but I need to verify this user can perform only end user roles. after this i want to create one more user say "ABC" as administrator. – Abhishek 6 hours ago
//adding comments
I am looking for, but when I am creating user in weblogic then only users are listing while creating Human task in my BPEL process. will you please tell me how to create users for worklist application. and the main problem is if I will create user in worklist and then how those user will be listed when creating Human Task.
just want to create two user , I will use them to login in work-list application, one for administration and one as a end user. All users what I am creating is showing administrative task tab. too much confused.
Thanks
Have you read this chapter of the developer guide :
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_worklist.htm#BHADHGCF
Have a look at this section "28.8.1 How To Manage Other Users' or Groups' Rules (as an Administrator)" : http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_worklist.htm#insertedID8
Edit :
Here the real solution :
Just follow this : http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10226/hwf_config.htm#insertedID7.
From the weblogic console, go to securityRealms | myRealms | users& group
Create a group , create your users, manage the users's group membership.
If I only set my new user in the new group, no administrative task tab is visible, but if I had the membership to the group labsupervisor, the tab is visible.
I know this is a bit old but i faced similar issue. Go to your domains config directory and add the ldap provider in the default jps context in jps-config.xml and it will work like charm :-)
<jpsContext name="default">
<serviceInstanceRef ref="credstore"/>
<serviceInstanceRef ref="keystore"/>
<serviceInstanceRef ref="policystore.xml"/>
<serviceInstanceRef ref="audit"/>
**<serviceInstanceRef ref="idstore.ldap"/>**
</jpsContext>
The properties for setting Managers can't be edited in the web console.
You need a LDAP client to connect the Weblogic's LDAP. There you will see the property "manager" for each user. Just add the DN of the user you want to be the manager for the selected user.
You can follow this tutorial:
http://jvzoggel.wordpress.com/2011/06/22/weblogic-embedded-ldap-with-an-external-ldap-client/

Devise: How to create a private admin role?

I have a simple Rails 3 blog app that needs an admin user so I can restrict creating and editing blog entries to the admin. I've used devise before, but only for users that are public and can be created by anyone. I don't want the ability to create an admin to be publicly accessible. How should I configure devise to be able to have an admin user?
Update:
After creating an Admin model, you might want to know how to create an admin that can log in (since you won't be able to register them on the front-end).
Have a look at the HOWTO in Github. There are basically two options:
Create a separate admin model
Add a admin attribute to the existing user model
I personally prefer option 1 for larger applications which tend to have different views for admins and normal users. For smaller apps I would recommend option 2.

Resources