There are 4 crucial topics we must discuses about, they are:
1. Outline security in the repository.
2. Exterior desk authentication.
3. LDAP authentication.
4. Database authentication.
Outline protection in the repository: In the Oracle BI Administration software we can produce users and groups to outline permissions and authentication. We then grant permissions to end users and teams.
Notice: The privileges which are completely granted to a consumer have precedence more than team's privileges. Also, in situation of a conflict the least restrictive privileges use.
LDAP Authentication: Numerous compnies want employing LDAP (Lightweight Directory Access Protocol) server authentication. quite a few consumers makes use of ADSI (Energetic Directory Services Interface) for their projects.
When questioned about how LDAP is set up you can say that, in the stability supervisor build an LDAP server. For this in stability manager we go to Action> New> LDAP Server. This delivers us to LDAP Server dialog box, exactly where we fill in the parameters like Title, Host Name, Port No., LDAP Model (Default 3), Foundation DN, Bind DN in general configurations. We also outline options in Sophisticated tab in which we fill in Connection Time-Out, Domain Identifier, Help / Disable SSL and many others.
We then designed an LDAP initialization block, which was linked with the LDAP Server. Below, we determine Consumer as our process variable which is mapped to LDAP uid.
Note: We can also use LDAP server only to import user and team definitions. This is made use of when we don't want exterior authentication by LDAP.
External Table Authentication: To employ this we have to produce a table in the databases which will have columns to outline end users, password, and teams, log level, display screen name, etc. details to outline protection and privileges. To use this desk for authentication in OBIEE we developed a new connection pool in the bodily layer to join to this db / table. Then we have to generate an initialization block making use of the newly outlined link pool for this desk. We then outlined the initialization string (eg decide on username, password, lognumber, groupname from auth_table in which username = ': User' and password = ': PASSWORD'). We then defined the corresponding variables (eg User, PASSWORD, LOGLEVEL, Group and so forth.). We have to make sure that the buy of variables is very same as the initialize.
Databases Authentication: We first make modifications in our NQSConfig.ini file. In the safety part, we specify our authentication databases. Then we develop buyers in the repository which are the exact as the consumers in our databases. We assign these users privileges. We import this database in the physical layer of our repository utilizing the DSN of that distinct databases. For this certain connection pool we set up a non shared logon. This connection pool will now be employed to join to the databases. If you are ready to link, then you are authenticated effectively.