Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
LDAP setup in RPD or new LDAP configuration in Console
Hi
We have upgraded our analytics application from 10g to 11.1.1.9.
As I heard LDAP setup is not supported in RPD configuration in 11g onwards, but after upgrading we are able to login to the application with LDAP users eventhough we have not configured LDAP setup in console.
The setup which was present in 10g still present in 11g RPD.
My question is, without any configuration how RPD ldap setup still works in 11g?
Do we need to configure in Console or will it be fine with RPD setup?
Thanks
Answers
-
Can you check if these users have been setup as WebLogic users? Check the WebLogic Admin console to verify that there are users there.
0 -
No, in Admin console these users are not present.
But still I am able to login to the application.
These users are not setup as weblogic user
0 -
If not wrong they still allowed the old config to work in 11g, that's why your system still works and you can login.
But that way of doing things is deprecated even if still there, so you better cleanup your RPD, remove the LDAP from there and do a proper config in Weblogic instead.
Users will not see any difference.
You also maybe still have things based on catalog groups: in that case you better start planning a move to application roles as those ones are deprecated in 12c, so when you will upgrade to 12c you will have a "translation" from groups to app roles and personally I would say it's better if you do it yourself instead of hoping the upgrade manage everything right ...
0 -
If you want to get problems out of the way and not be in troubles at the next upgrade again....do it correctly right away. Go for the LDAP connection config in the WLS security realms.
Because 11.1.1.9 - while still supported - is old and will only ever be an intermediary step.
0
