• State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 5887 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AD Account Provisioning Error. Corporate policy violation

yahya.said
over 6 years ago

Hello Everyone, 

I have just run in to an error whilst trying to provision an AD Account using an Account definition. 

Just to give some background information, I am using the ARS connector to connect to their AD environment. I am able to pull in information with a sync and was even able to provision AD accounts perfectly up until recently.

It turned out that the customer didn't transfer the policies from their production environment in to Dev / UAT and all of a sudden, i am now not able to provision after the move. 

I have been working with the AD admin and have met all of the requirements for the policies however it doesn't seem to be making any difference. 

For example the error in the screenshot below shows that the Firstname / Givenname property does not conform to their policy. I don't understand how this is occurring as the policy just states that the field should be mandatory and before the policies were applied, it was creating AD accounts using this property.

I have seen the page for a similar issue in ARS and have referred it to the Admin. 

https://support.oneidentity.com/active-roles/kb/215373 

 

Also I am using v7.1

Any help or guidance would be greatly appreciated

 

Thanks 

Yahya

Parents
  • 0 over 6 years ago

    That error is coming for Active Roles and it is basically saying that the parameters provided for First Name does not comply to the current policy applied to the OU in Active Roles. I would check within Active Roles to see which policy is currently applied to that specific OU.

     

    I would then attempt to create a test user within Active Roles in that same OU and use a similar first name as the user trying to be created via identity manager

     

    I would imagine that you get the exact same error message

Reply
  • 0 over 6 years ago

    That error is coming for Active Roles and it is basically saying that the parameters provided for First Name does not comply to the current policy applied to the OU in Active Roles. I would check within Active Roles to see which policy is currently applied to that specific OU.

     

    I would then attempt to create a test user within Active Roles in that same OU and use a similar first name as the user trying to be created via identity manager

     

    I would imagine that you get the exact same error message

Children
No Data