Categories
Configure LDAP in OAS 5.5.0 [Windows Installation]

Hi,
I have installed OAS 5.5.0 on Windows Server and it's working fine.
Next I want configure LDAP Authenticator in OAS 5.5.0
In WLS Console in Security Realms / myrealm / Providers / new provider as ADAuthenticator
I think that is working fine because in WLS Console I see User and Groups from customer AD.
Next I want add user to application role in Enterprise Manager but I can not see LDAP Users in EM - what I shoud to do? I only see users from default provider as weblogic and my test user.
I add in Identity Store Configuration / Customer Properties / virtualize = true ---restart all servers -- but it's not working. Additionaly when I add virtualize = true --- in 'host:9502/dv/ui/home.jsp?pageid=console' in Users and Roles I do not see anything:
How I should configure 'LDAP Authenticator' in EM or in OAS?
Answers
-
The integration works 1:1 as it did before. What LDAP are you accessing? SSL or non SSL? Actual LDAP or MSAD or what? What do the bi_server1 logs say? Where do the errors occur? EM reads the auth providers via OPSS so you've gotta have an issue somewhere in that chain.
0 -
@Christian Berg thanks for response.
LDAP:
- non-ssl -- on the older server SSLEnabled is uncheck in WLS Console
- actual LDAP -- but I am waiting for customer feedback
What I did:
- configure LDAP in WLS Console (new provider: ADAuthenticator, set flag:SUFICIENT and set this flag SUFICIENT in DefaultAuthenticator)
- test in WLS Console after restart - I see users and group from AD
- in EM i set: virtualize = true and OPTIMIZE_SEARCH = true, next I restart services and I not see in EM user from LDAP - I can't add for this user applications roles..
What I check:
- the file in BI_DOMAIN\config\fmwconfig\ovd\default\adapters.xml not update with new provider - i think something wrong ?
Maybe must I get from customer 'root certification' and do something in OAS? Or why this no update with restart?
0 -
ADAuthenticator ==> That's Microsoft Active Directory
Is the ADAuthenticator first in the sort order?
You must restart after the whole config. So after setting virtualize.
0 -
Maybe, in wls console it looks like:
Yes - ADAuthenticator is first order, DefaultAuthenticator is second/
I restart all services at now after everthin setting - but it is not help.
But why file in: BI_DOMAIN\config\fmwconfig\ovd\default\adapters.os_xml not update? It has only defaultauthenticator - maybe here is the problem?
When I list adapters I only see:
but conif.xml has AdAuthenticator...
0 -
What the hell? How can that not e written to the adapters? I just did it in OAS and that file still has all.
Drop the provider and recreate from scratch. Something's fishy
0