Skip to Main Content
Forums

Security Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

WebLogic integration with Active Directory for authentication provider

Sandeep Kumar skMar 31 2019 — edited Sep 15 2020

I am configuring WebLogic 12c with Active Directory as a Provider and have few questions if someone has done a WebLogic integration with Active Directory.

For the WebLogic Provider configuration 1), 2), 3)

1) Host:          For the hostname of the Active Directory Domain Controller, can we put multiple hosts, comma separated? Since there are multiple domain controllers.

2) User DN:   Can we provide the base DN of the users in AD (like DN=Users, dc=example,dc=com). Is this top level DN allowed?  (Note, we tested with one user first and provided his particular DN. Since the users are spread across various OU we wanted to make sure authentication works fine for one user, which does work fine)

3) Group DN:  Do we require a special group in AD where all the users can be put in? And this group needs to be put in the Group info in the WebLogic configuration in the Provider settings?

For weblogic.xml configuration

4) One of the step is configuring weblogic.xml file. Here we have provided username of a particular user and his particular DN, for a test and authentication works fine with below settings. However these settings are for a particular user. What needs to be put in for "principal-name" so that all/other users can also login? Similarly what needs to be put in for "role-name"?

<wls:security-role-assignment>

    <wls:role-name>Valid Users</wls:role-name>

    <wls:principal-name>userabc</wls:principal-name>

</wls:security-role-assignment>
This post has been answered by User_886HI on Apr 1 2019
Jump to Answer

Comments

Alex Keh-Oracle
Answer

The current async implementation, task-based, is the third .NET iteration for asynchronous programming models. Before task-based async, there was event-based pattern and the async programming model. .NET async programming patterns have been around since near the beginning of .NET FW itself. And the reason why these async models have changed over time is because there was never a popular async model until the most recent iteration.

And therein lies the reason why ODP.NET has taken a wait and see approach. Async .NET programming is not new, but historically it had never gone mainstream.

With that said, Oracle is working on supporting task-based async. We'll have more details during Oracle OpenWorld in September.

Marked as Answer by OnurGumus · Sep 27 2020
OnurGumus

Dear Alex,

I disagree with your below comment:

" Async .NET programming is not new, but historically it had never gone mainstream."

As of now except Oracle, all database vendors that support .NET, also support proper asynchronous API.

Alex Keh-Oracle

Hi Onur,

What I meant by that statement was that the event-based pattern and the async programming model were not popular among .NET developers and eventually abandoned by Microsoft. Vendors who devoted much effort to supporting those earlier two models had to invest yet again in async with the task-based async pattern. Oracle has approached supporting a new async pattern relatively cautiously when noting the history.

user12186381

Hi Alex,

Any plans to make the async make GA?

I see that we have a pre-release available, but clearly states that should be used in Production Environments.

I'm just waiting for the final release to start using it in our projects.

Thanks,

Alex Keh-Oracle

ODP.NET Async is part of 23c client. When 23c DB goes GA, the client will also be GA.

The plan is to have DB 23c GA in the first half of 2024.

1 - 5

Post Details

Added on Mar 31 2019
#identity-management, #identity-manager, #weblogic
3 comments
418 views