MSFT_AD_Base_11.1.1.5.0
hi
I've new installation of oim 11g (bp4)
new ad connector MSFT_AD_Base_11.1.1.5.0
manual provision works fine
but when I'm using access policy to provision ad resource to user process stacks on running pre-pop adapters
Running CONCATFIRSTANDLAST
Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
Running CONCATDOMAIN
Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
Running CONCATUSERLOGINWITHDOMAIN
Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
and that's all
I've check auto save form and auto pre-populate checkbox status, but both set to true
in resource history still System Validation and status Pending
resource form clear
all mandatory fields contains values from access policy or from pre-pop
from AP
ITresource
Password
OU
from prepop
User Id
First Name
Last Name
Middle Name
Full Name
Common Name
User Principal Name
but when provision starts from AP in log I see only adapter working for User Principal Name
Similar Messages
-
Auto provisioning for AD is not working in oim11gr2
Hi All,
I have current environment as OIM 11.1.2.0.7 and AD connector MSFT_AD_Base_11.1.1.5.0 with patch applied 14190610 and Connector_Server_111200
I configured an auto provisioning to AD
I created an access policy based on a role MSAD Users.
i am expecting when i assign this role user should provisioned to AD automatically but it is not done. I also ran the Evaluate User policies scheduler which in enable state.
i provisioned user manualy and its working fine. also i checked access policy with another target application R12 application it is also working fine.
but i dont y it not working for AD . I filled all required fields in process form lyk organisation and AD Server.
I ran in to same issue in DEV at that time i applied BP07 to oim and 14190610 patch to AD connector, after that it was worked
Now my UAT is in same environment still it is not working
Please suggest me some solution
Regards
$sidHi All,
I have current environment as OIM 11.1.2.0.7 and AD connector MSFT_AD_Base_11.1.1.5.0 with patch applied 14190610 and Connector_Server_111200
I configured an auto provisioning to AD
I created an access policy based on a role MSAD Users.
i am expecting when i assign this role user should provisioned to AD automatically but it is not done. I also ran the Evaluate User policies scheduler which in enable state.
i provisioned user manualy and its working fine. also i checked access policy with another target application R12 application it is also working fine.
but i dont y it not working for AD . I filled all required fields in process form lyk organisation and AD Server.
I ran in to same issue in DEV at that time i applied BP07 to oim and 14190610 patch to AD connector, after that it was worked
Now my UAT is in same environment still it is not working
Please suggest me some solution
Regards
$sid
Maybe you are looking for
-
How to Release Mass Purchase order in production server
Hi i have to release mass purchase order can any one help me how to that thanx
-
Routers that work with iChat AV?
Since Apple's list of approved routers hasn't been updated for years, I would love to hear from anyone who has purchased a router recently that works with iChat for audio/video, including any special setting changes/tips. Could anyone with a success
-
Windows service, error Maximum request length exceeded
What is causing this error, from the windows service? There was an exception running the extensions specified in the config file. ---> Maximum request length exceeded
-
Hi. I wish to submit feedback, so I click "help" then "Submit feedback". I get directed to a page: Oh! So, you want to offer us feedback on Firefox. Thank you, but you'll need to be on the latest version. To do that, simply go to our download page an
-
Password policy not allowing to reconfigure STMS
Hi Guru's, I have done system copy by database restore method, in post activities I have mistakenly deleted STMS configuration on domain controller, now when I am trying to add production server in landscape. the password policy is not allowing us to