I have a liferay instance instance running on websphere7.0, RHEL 5 which is connected to my organization's Active Directory.
I have a requirement where the user in liferay database should get automatically deactivated when that user is deleted from the AD.
The basic liferay functionality is that if a user is deleted from the AD, that user doesn't get deleted or deactivated in liferay. The only thing we can control from the control panel is that whether that deleted user(from AD) can log into the portal or not.
I searched and found that we can LDAPImportMessageListener class to customize the basic liferay behavior. But i am sure how to do that.
Please help.
Delete / Deactivate user in Liferay is not implement OOB when user deleted from AD, You would need to add your implementation by extending PortalLDAPImporterImpl.java
Related
My demo app uses Azure AD B2C. Since it's a B2C, new users can create their own account. When a new user joins, I want:
to event grid to start a Logic app
the logic app will grab some of the data update the CosmosDb containers
send an email to the new user
deliver a message that any subscriber can read
I'm stuck in the beginning because I can't find anything that it's related to Azure Active Directory. I can't find a tutorial or any information related to tha.
My question is to know whether event grid can even be used to react to users being created in Azure AD?
Thanks for helping.
I don't think this trigger can implement your requirement. As we can see it requires us to choose Resource Type, Resource Name... But users do not belong to resources, resources refer to storage, VM, keyvault and so on.
So for your question about
whether event grid can even be used to react to users being created in Azure AD
I think it can't be used to react to users being created in Azure AD.
I installed a Kentico 9.0 website and everything worked fine. Then I tried to configure Windows Active Directory authentication using this documentation: https://docs.kentico.com/display/K8/Configuring+Windows+AD+authentication. However, when I open the URL, the login popped up, I used my working login credentials and the login pops up back constantly.
I changed back the web.config and saw the event log, and there was nothing logged about my numourous login attemps.
The documentation was straight forward, so I am guessing there is a permission issue in my environment. There is one little warning in the documentation but it doesn't say how to do it:
Prerequisite
For Windows authentication to work, the application must be able to access the following attributes of user objects in Active Directory (i.e. the attributes cannot be protected or confidential):
memberof
userAccountControl
My application is in a virtual server in a domain. And the Active Directory service is in different server in the domain. Does it mean I need to do something for my application's permission to AD? I am using NetworkServices application pool identity.
Thanks.
You (your laptop) have to be in company intranet and logged in to your laptop with your AD credentials. If you meet those conditions IE or Chrome should not even prompt you for credentials as they are already known, so browser just passes your AD account information to Kentico.
Once you see the prompt continuously there is something wrong with your setup. Make sure
you configured everything according to documentation (Kentico + IIS)
server/host is in domain
you're in intranet and logged in with AD creds
Usually how Active Directory authentication works is you need to pass it a AD Username and password that has access to read the users. I would check that user's permissions.
I've implemented a site using Umbraco 7.1.3 and configured the CMS to use Active Directory for the login. I've followed this official post (https://our.umbraco.org/wiki/how-tos/membership-providers/active-directory-membership-provider) and everything works perfectly.
My problem is when I try to create a new user using a user which has successfully logged in using It's AD credentials. Obviously the user I'm using is an Administrator of the CMS.
When I try to create this second user I get an error which points that
login name already exists
I can't find or understand what is doing Umbraco when it's configured to use AD as DefaultBackofficeProvider.
Does it try to create an user in Active Directory?
As I thought, the CMS will use the AD as the store of users, but it doesn't create new AD users for you (effectively you can only use the users section in the CMS to assign permission to users who have logged in).
If you wanted the Users section to create AD users for you, you might be able to code something custom yourself?
I am using active directory to authenticate users on my DNN portal. It's been working fine but recently it does not allow some of the users into the site. It brings the server error (404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.)
The funny thing is that not all the users are having this problem, only a few does. I checked in my Users table and these users exists and they have both the Registered Users and Subscribers roles.
I am running on DNN 4.7.0.
Your help will be highly appreciated.
can use please check that user belongs to all portals or portal have different user
in dnn if you create a user in one portal than it is not accessible outside of that portal
We have installed SharePoint Server 2010 and Project Server 2010 without AD. We're a disconnected bunch and thought we'd take it for a spin since being part of BizSpark. But now I'm seeing an issue with editing user account info like email address. Can anyone give me some hints on how life might be like without AD or how to supplement what we might be missing by running the system without AD. Many posts note it is supported but little has notes on what you might be missing.
Thanks in advance.
What you need is to check out the User Profile Service Application area.
Go to SharePoint Central Administration
Go to Manage Service Applications
Select User Profile Service Application
This area is the home of the accounts that are in SharePoint, as well as all the information about the users and how it is displayed on their "My Site"/profile page areas.
If you select Manage User Profiles, this is the area where you can override information from Active Directory about users that are in sharepoint. If you connect to AD, you'll see a little database icon next to the fields that indicates it is synchronized. Even if you use AD, these field can be individually overriden with new information. If you don't have AD, then these will all need to be populated manually by you.
If you go to Manage User Properties you will find all the options to show which fields are editable and which fields are not on a user's profile. This includes, but is not limited to:
Email
Display Name
Homepage/Url
Department
Manager
If you have AD, you'll rarely visit this service admin page, because everything will just work. If you don't, then you'll need to check out this area to change the information about the people that are using your SharePoint instance.
Hope that helps!