One of our applications uses AD with remote_os_authent for single sign on (for some users) to the underlying database.
The database is currently on 9iR2 but will soon be moved to 11gR2 - with remote_os_authent now deprecated, I am under the impression from the vendor that one has to now add Oracles Access Manager with it's extra cost now that remote_os_authent is being phased out.
The vendor's app is tied in with Microsoft Active Directory to pass along credentials to implement single sign on, as a result of remote_os_authent being deprecated they tell me many of their customers are balking at purchasing an additional license(s) so they have now ported the application to use MSSQL database for a back end, as MSSQL provides integration with AD at no extra cost. This is an option I have been asked to look into as well, if there is going to be an extra cost to what we've already been using at no cost.
I've not had a lot of experience with remote_os_authent, and am confused if integrating database logins with AD specifically requires the remote_os_authent parameter or one can create a user identified externally and have AD pass the domain credentials without the remote_os_authent parameter. We have EE licensing and if I have to purchase an additional product at an additional cost now then I'll likely look at having them port the app to use MSSQL as well.
Anyone else running into this?
thanks in advance