useraccountcontrol not available as Active Directory Attribute Skip to main content
https://support.okta.com/help/answers?id=9060z00000078kcqai&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Gareth EvansGareth Evans 

useraccountcontrol not available as Active Directory Attribute

Am i missing something here? looking at all the available AD attributes that i can import the only one that seems to be not available is UserAccountControl, previously with FIM we used this attribute quite a lot and planned to use it here as an example:

Provision application to users only if there accounts are not set to never expire/not disabled (User account control value 512).

In fact we use 512 quite a lot as a way of filtering out system, service and resource accounts.

any thoughts?

thanks.
Andrei AldeaAndrei Aldea (Okta, Inc.)
Hi Gareth,

Apologies for the late reply on this - it is expected behavior that the userAccountControl attribute cannot be added to the list of AD Attributes. Okta already reads this attribute value for the purposes of determining if a user has been deactivated.

This article (https://help.okta.com/en/prod/Content/Topics/Directory/Directory_AD_Field_Mappings.htm) goes into a bit more detail regarding this:

"The system treats previously imported users as deleted if any of the following conditions are met:

-The userAccountControl attribute indicates that the user has been deactivated. (Detected by incremental import or JIT sign in.)"

However, it should still be possible to bring in the value of the attribute into Okta, by using a different AD Attribute for that purpose.


Thank You,

Andrei Aldea
Technical Support Engineer
Okta Global Customer Care