Hello,
I'm using property pattern for few things, and i just noticed that all my property pattern are applied on user creation (i don't want it to)
Is there a way to "disable" property pattern on user creation ?
Hi,
for this purpose I created a specifc "Creation" OU and excluded the default property patterns for this OU.
Then I created a new pattern for only my creation OU.
Hope this helps
It is not possible to make a property pattern not act upon user creation. The approach suggested by wintec01 is the only option.
Is there a way I can bypass a property pattern for a set of users? For example we have an AP team that creates an account and want to restrict Job Title and Department to a ... we would like to be able to override that list. Is there an easy way to do that?
Adaxes uses a property pattern file for creating and modifying an user. Is it possible to have a property pattern file for creating or modifying only? I try to achieve the ... required when an user is created but not required when an user is modified... Remco
I've noticed that sometimes when users are added to groups, the timestamp of the user object is not updated. If you execute LDAP queries against the modifytimestamp field, this creates ... (as seen in the web interface) (scroll to right to see entire image):
I have a specific computer property pattern for three different types of computers, which live in three different OUs and are in three different business units. I will have ... How do I enforce a property pattern for a specific business unit at creation time?
I am trying to use a property pattern to prevent email forwarding to accounts in other domains managed by Adaxes. Here is my regex: ^([^,]+,)+(DC=domain,DC=local) ... 't working? Is Adaxes using some other value before resolving the DN? Thanks in advance! Leah