Add an Oracle BI Enterprise Edition Application
This page describes process of configuring an Oracle BI Enterprise Edition application through the Access Gateway AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. Console.
- Access Gateway is installed and configured for use.
See Manage Access Gateway deployment.
- Access Gateway has been configured to use your Okta tenant as IDPAn acronym for Identity Provider. It is a service that manages end user accounts analogous to user directories such as LDAP and Active Directory, and can send SAML responses to SPs to authenticate end users. Within this scenario, the IdP is Okta..
See Configure your Okta tenant as Identity Provider for more information about configuring your Okta tenant as an IDP.
- You have administrator rights on your Okta tenant and can assign applications to users, and create groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups..
- The protected Oracle BI Enterprise Edition resource has been configured to trust incoming messages and to support SSOAn acronym for single sign-on. In a SSO system, a user logs in once to the system and can access multiple systems without being prompted to sign in for each one. Okta is a cloud-based SSO platform that allows users to enter one name and password to access multiple applications. Users can access all of their web applications, both behind the firewall and in the cloud, with a single sign in. Okta provides a seamless experience across PCs, laptops, tablets, and smartphones. (User identity and SSO cookie in header)
- An external Oracle Access Gateway Server based application which requires protection.
- Appropriate DNS entries for both the legacy application and the exposed new URL exist.
- Appropriate DNS entries for both the protected application and the external URL for example:
Value Description https://obiee.externalexample.com External or customer facing application URL. https://obiee.internalexample.com
Internal or protected application URL of an Oracle BI Enterprise Edition application.
In the Access Gateway Admin UI, sign in as an administrator.
Click the Applications tab.
Click +Add to add a new application.
Select the Oracle WebLogic option from the left column menu, and click Create.
The New Protected Application wizard will start and display the Essentials pane for the application being added.
In the Essentials pane specify the following:
Field Value Label A name for the application such as "Oracle Hypersion application" Public Domain A fully qualified host name such as <yourexteralname>.<your domainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https).>.
In the example provided this would beobiee.externalexample.com.
Protected Web Resource
The URL of the internal, protected, application.
In the example provided this would be obiee.internalexample.com:<port>
- port - the port Oracle BI Enterprise Edition is listening on for http requests.
Group Enter the group containing the users who should have access to the application.
Post Login URL
Enter or modify the post login URL. By default this field is enabled and contains value:
Description [optional] An appropriate description for your application.
The Attributes page provides a list of attributes that will be
passed into the application as header fields.
Use edit () to modify the name and other values associated with the attribute if required.
Add or modify any additional required attributes, and click Next.
For more information on the attribute options, see Application attributes.
. The Policies pane appears.
- Leave all policies unchanged and click Done.
For more information on Application policies seeAbout application policy
The following steps assign the application to a test account and then execute the application to verify basic functionality.
Assign the application
Login to your Okta tenant as administrator.
Select Application > Applications.
Click the name of the newly added header application.
Select the Assignments tab.
Select Assign > Assign To People.
Select an appropriate user and click Assign.
Testing is typically initially done using the same user who is associated with administering Access Gateway
Execute the Application
Return to the Access Gateway admin console.
On the row representing the newly added appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in., select one of Goto application > IDP Initiated or Goto application > SPAn acronym for service provider. Generally, an SP is a company, usually providing organizations with communications, storage, processing, and a host of other services. Within Okta, it is any website that accepts SAML responses as a way of signing in users, and has the ability to redirect a user to an IdP (e.g., Okta) to begin the authentication process. Initiated.
- Verify the resulting page displays as expected.
- Close the results page.
- Add or review application essential settings. For more details see About application essentials and Manage application essentials.
- Add application behaviors. For details and examples of behaviors see About application behaviors
- Add fine grained policy to further protect resources. An overview of user policy can be found in About application policy.
For details and examples of policy see Manage application policy .
- Extend existing policy using Custom configuration, seeAdvanced Access Gateway Policy.
- Define one or more certificates for use with this application. SeeConfigure certificates
- Add supplemental database or LDAPLightweight Directory Access Protocol (LDAP) is a lightweight client-server protocol for accessing directory services, specifically X.500-based directory services. LDAP runs over TCP/IP or other connection oriented transfer services. based data stores. For more information see Administer data stores.