If you want to be able to do SSO, especially if you want SSO with windows AD, then using the AD user ID as the user id in EBS would be recommended as that would make it much easier to implement SSO. You will need Oracle Access Manager 11gR2 as well as Oracle Internet Directory and DIP in order to implement SSO for EBS and use your AD accounts.
Thanks for your reply Handat.
Is these modules - Access Manager , Internet Directory, DIP- are free or we need buy.
They are part of the Oracle Access Management Suite and licensed accordingly. I am not sure if EBS includes a restricted license to implement it for SSO. Check with your Oracle sales rep or perhaps someone on this forum with that knowledge might chip in.
Checked with consultants - below are the initial technical requirements . As this will process will take more time to get internal approval, we are going ahead with company Employee ID as the ERP user id. Thanks
- Oracle Access Manager 126.96.36.199.0, 188.8.131.52.0
- See Footnote 1 for restrictions.
- Oracle Access Manager WebGate
- Oracle Identity Management 184.108.40.206.0, 220.127.116.11.0
- Oracle Unified Directory 18.104.22.168
Good luck with that especially with your later stages as you will need a lot of it. It may seem like good progress at the moment to be able to continue quickly, but you may regret it later on when this decision will bite you during the SSO or provisioning part of the work. Make sure this decision is documented properly in the architecture and pros and cons are well understood. I am not saying that this means doom, but it will cost you a lot in terms of efforts during the SSO/provisioning work so keep in mind that the guestimate effort you will be given for that piece of work will need to at least trippled.